Re: Considering the Nexus repository infrastructure for our future releases?

2010-03-12 Thread Emmanuel Lecharny
On 3/12/10 7:45 AM, Stefan Seelmann wrote: I use Nexus in my current project as repository and it works very well. So my +1 for that step. +1 too. If it offers a better support for our releases, I don't see why we should not switch. -- Regards, Cordialement, Emmanuel LĂ©charny

Re: Considering the Nexus repository infrastructure for our future releases?

2010-03-12 Thread Pierre-Arnaud Marcelot
Hi Felix, I'm not really sure yet, but I'm afraid this won't work for the deployment of the generated documentation. Maybe we should ask the infra guys about that. However, I think a good workaround could be to have the documentation in a dedicated (empty) local repository that you can then

Re: Considering the Nexus repository infrastructure for our future releases?

2010-03-12 Thread Felix Knecht
Am 12.03.2010 13:25, schrieb Pierre-Arnaud Marcelot: Hi Felix, I'm not really sure yet, but I'm afraid this won't work for the deployment of the generated documentation. Maybe we should ask the infra guys about that. However, I think a good workaround could be to have the documentation in a

Re: Considering the Nexus repository infrastructure for our future releases?

2010-03-12 Thread Pierre-Arnaud Marcelot
On 12 mars 2010, at 13:33, Felix Knecht wrote: So we keep the keep it as is. After building a release we build the documentation and deploy it to p.a.o manually. That's also ok. Well I thought the generated doc was deployed automatically via scp by maven, was I wrong ? I'm not really a pro

Re: Considering the Nexus repository infrastructure for our future releases?

2010-03-12 Thread Felix Knecht
Am 12.03.2010 13:44, schrieb Pierre-Arnaud Marcelot: On 12 mars 2010, at 13:33, Felix Knecht wrote: So we keep the keep it as is. After building a release we build the documentation and deploy it to p.a.o manually. That's also ok. Well I thought the generated doc was deployed

Re: Considering the Nexus repository infrastructure for our future releases?

2010-03-12 Thread Pierre-Arnaud Marcelot
On 12 mars 2010, at 13:56, Felix Knecht wrote: It looks like the Nexus Professional does have such a feature, but I don't now which Nexus is used and if (whenever) it's enabled and used. See 'Hosting Project Web Sites' [1] Interesting... Version used at the ASF is: Sonatype Nexus™

Considering the Nexus repository infrastructure for our future releases?

2010-03-11 Thread Pierre-Arnaud Marcelot
Hi everyone, I'd like to propose that we use Apache's Nexus repository infrastructure to release our future versions on Maven repositories. It's used by a large number of Maven based Apache projects now, and it's the recommended way of uploading releases to Maven Repositories, as described on

Re: Considering the Nexus repository infrastructure for our future releases?

2010-03-11 Thread Jesse McConnell
fwiw we do this with jetty and its awesome... the support for staging is awesome...makes life and votes and things like that very simple cheers, jesse -- jesse mcconnell jesse.mcconn...@gmail.com On Thu, Mar 11, 2010 at 11:41, Pierre-Arnaud Marcelot p...@marcelot.net wrote: Hi everyone,

Re: Considering the Nexus repository infrastructure for our future releases?

2010-03-11 Thread Stefan Seelmann
I use Nexus in my current project as repository and it works very well. So my +1 for that step. Kind Regards, Stefan Pierre-Arnaud Marcelot wrote: Hi everyone, I'd like to propose that we use Apache's Nexus repository infrastructure to release our future versions on Maven repositories.