Re: [dash-dev] Maven Nexus server

[Alex Blewitt <alex.blewitt@xxxxxxxxx>]

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