Re: [hudson-dev] Hudson on hudson and local nexus?

[Henrik Lynggaard Hansen <henrik@xxxxxxx>]

Hi

It is not us who are using strange dependencies, but some of the
plugins we have in our update centre does. I want to also build those
for early testing

There are several issues:

1) The issue about maven3 dying unless I mirror glassfish to the
jenkins repository
https://bugs.eclipse.org/bugs/show_bug.cgi?id=376785

2) I generally don't like it when builds access repository groups
where the real repositories are hidden behind a proxy because it many
times leads to pom files which aren't correct since they don't specify
the real repository dependencies. it makes them brittle and error
prone.

Sadly the jenkins plugin uses this approach and just specify the
"public group" as where they can find there parent.I have already seen
at least one didn't specify a correct repo for its guice dependency

3) The plugin tester framework relies on querying the remote repos in
order to identify available versions of a given plugin or core. I
would really like this to include snapshot versions, but there is no
reliable place to find these snapshot versions. They don't seem to
exist in any repositories. Therefor it would be great if we could
publish the plugins+core we build to a "alternate" snapshots repo

4) I am not sure about how to handle this, but at leats one hudson
plugin is dependent on artifacts that cannot be found in the open
repositories

We could lock it down completely, so that nothing can be downloaded
from it without username/password

I don't know the glassfish history, so you can better judge if we are
heading in the wrong directtion


Best regards
Henrik





2012/4/17 Winston Prakash <winston.prakash@xxxxxxxxx>:
> Henrik,
>
> If it is really necessary we could do that. But Glassfish maven started
> as a local Nexus and ended up problematic in the end. IMO, what ever
> artifacts we use must be in the maven central. What kind of artifacts
> are missing?
>
>
> - Winston
>
> On 4/17/12 8:55 AM, Henrik Lynggaard Hansen wrote:
>> Hi
>>
>> One of the things I have noticed when building some of the tier 2+3
>> plugins is that many have not very well defined maven pom files, so
>> many times I use my local nexus in conjunction with a detailed
>> settings.xml to remedy that.
>>
>> Can we have a small nexus on our infrastructure?
>>
>> Best regards
>> Henrik
>> _______________________________________________
>> hudson-dev mailing list
>> hudson-dev@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/hudson-dev