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

["Manfred Moser" <manfred@xxxxxxxxxxxxxxxx>]

That would just replace one repo with another repo that could fail. You
should figure out which artifacts are not on central that are needed by
the build and get these there and then get rid of the dependency on the
glassfish repo.

Last time I tried that it was only one unit testing related library ..

manfred

On Wed, April 18, 2012 1:10 pm, Henrik Lynggaard Hansen wrote:
> Hi
>
> If you look at the hudson on hudson now you will see that many jobs
> are failing because of corrupt artifacts. I think it is because of the
> broken glasfish.
>
> I think we need a local nexus to clean this up.
>
> 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
> _______________________________________________
> hudson-dev mailing list
> hudson-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/hudson-dev
>