Re: [dash-dev] Maven Nexus server

[Andrew Ross <andrew.ross@xxxxxxxxxxx>]

Hi Everyone,

Sounds like fairly easy agreement that a well managed Nexus repository would be of benefit to the community and that it makes sense to "reboot" maven.eclipse.org. For what it's worth I can see obvious benefit and synergy with the CBI efforts and the Long Term Support (LTS) program as well - thus I can make a pretty clear business case that we simply need to do this.

I'm hoping that we can lean on you all a bit longer for your help to capture lessons learned from maven.eclipse.org to date, sort through bugs and requirements, and help figure out how we should implement the new system? If you feel like being part of this, please +1 to register your interest.

In terms of timing, the work on the CBI build for the Eclipse platform 
is taking a bit longer due to vacations and competing other demands so may not be 
ready for SR1. This will slip when we can start picking up work with 
Nexus by weeks. You can follow along on cbi-dev to track progress. I'm cautiously optimistic the slip won't be too bad due in part by some great work and persistence by Igor, Chris, Thanh, Paul, and others. We can always use a few more hands testing if you're interested to help speed us up.

Also, I'm inclined to simply leave maven.eclipse.org for now and start a new instance in parallel for fear of disruption to anyone using it.

Andrew

On 15 August 2012 20:05, Igor Fedorenko <ifedorenko@xxxxxxxxxxxx> wrote:

I do not decide what is and is not part of CBI effort. You need to talk
to Andrew Ross to see if he feels they have resources and expertise
needed to take over maven.eclipse.org.

Personally, I do think that supported and well-maintained Maven/Nexus
hosted repository will benefit Eclipse community in general, but I also
think that Foundation (or should it be Planning Council?) will need to
make policy decisions before anything happens.

--
Regards,
Igor

On 12-08-15 6:34 PM, Alex Blewitt wrote:

I mentioned to Igor that I'd be happy if they wanted to take it over but he didn't seem interested.

I do think it is at a stage that it needs more than just community ownership though, especially when problems occur during working hours when it isn't possible for us to intervene.

Alex


Sent from my iPhone 4S

On 15 Aug 2012, at 23:29, Jesse McConnell <jesse.mcconnell@xxxxxxxxx> wrote:

+1 for CBI, I know they are planning on looking into the orbit mess as
well once SR1 is done

orbit mess being how to reconcile orbit with maven central in a sane fashion

jesse

--
jesse mcconnell
jesse.mcconnell@xxxxxxxxx


On Wed, Aug 15, 2012 at 5:24 PM, David Carver <d_a_carver@xxxxxxxxx> wrote:

Personally, with CBI using maven.  I'd actually recommend that Nexus server
fall under that group. Especially with Nexus 2.1.x able to support p2
repositories, and also make existing maven repositories p2 enabled.   So
items could technically just be deployed to it and the basic p2 metadata is
generated as needed.

Dave



On 15 Aug 2012, at 21:45, Alex Blewitt wrote:

We've run out of disk space again - I'm trying to clean it up, but
there's something on the filesystem which appears to be taking a lot of
size. Right now the server is in the process of trying to restart and
generating errors in the log files, probably due to lack of space.

So I've cleaned out some cruft, but I think it's likely to recur. The
performance of the virtual disk is horribly slow and although the nexus jobs
are set up to purge the trash and remove unused items, I think that there's
a number of people hitting http://maven.eclipse.org for non-eclipse content.

There's also some data in /var which we can clean - there's a lot of data
in /var/messages, for example. However, the root password (was in ~admin/pw,
now gone) seems to have gone walkabout - anyone know where it went?

Finally, I'm concerned that the level of support (and management) that we
(as Dash) are able to provide doesn't fit the Eclipse organisation. Given
that we haven't succeeded in converting Eclipse to Maven hosting - and the
m4e tools never made it to production worthy status - I'm wondering if we
shouldn't shut the system down. Unfortunately, I don't know where the
repository is being used from hudson slaves, so I'm not sure if that's even
practical - or whether the repositories are being used by others.

Thoughts?

Alex
_______________________________________________
dash-dev mailing list
dash-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dash-dev

_______________________________________________
dash-dev mailing list
dash-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dash-dev

_______________________________________________
dash-dev mailing list
dash-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dash-dev

_______________________________________________
dash-dev mailing list
dash-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dash-dev

_______________________________________________
dash-dev mailing list
dash-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dash-dev