You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by Pierre-Arnaud Marcelot <pa...@marcelot.net> on 2010/03/11 18:41:46 UTC
Considering the Nexus repository infrastructure for our future releases?
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 the "Releasing A Maven Project" Guide [1].
I think we've reach the limit with deployments on people.apache.org... My last deployment of Studio for version 1.5.2 took more than four hours (!!).
I talked with Chris Custine on that subject and we would probably have a much better performance with Nexus. It also have pretty neat features like stagging that would allow us to upload artifacts and approve (or deny) them later, which could be interesting when voting a release.
However, there's seem to be one "drawback" in the fact that once the project is moved to Nexus, deployment on people.apache.org are disabled. All deployments must be done on Nexus.
More information on this on this at INFRA-1896 [2].
I would really like that we discuss that all together and maybe we could launch a vote to move to Nexus after this discussion.
WDYT?
Thanks,
Pierre-Arnaud
[1] - http://maven.apache.org/developers/release/apache-release.html
[2] - https://issues.apache.org/jira/browse/INFRA-1896
Re: Considering the Nexus repository infrastructure for our future releases?
Posted by Pierre-Arnaud Marcelot <pa...@marcelot.net>.
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™ Professional Edition, Version: 1.5.0.1
However, I have no idea if this feature is enabled or used at the moment.
Pierre-Arnaud
Re: Considering the Nexus repository infrastructure for our future
releases?
Posted by Felix Knecht <fe...@apache.org>.
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 automatically via scp by maven, was I wrong ?
>
> I'm not really a pro of Nexus yet.
> I've just installed it and I'm currently trying it on my local machine.
> I have not idea if Nexus can handle documentation releases.
> I'm going to test that.
>
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]
Felix
[1]
http://www.sonatype.com/books/nexus-book/reference/ch01s03.html#intro-sect-pro-features
Re: Considering the Nexus repository infrastructure for our future releases?
Posted by Pierre-Arnaud Marcelot <pa...@marcelot.net>.
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 of Nexus yet.
I've just installed it and I'm currently trying it on my local machine.
I have not idea if Nexus can handle documentation releases.
I'm going to test that.
Pierre-Arnaud
Re: Considering the Nexus repository infrastructure for our future
releases?
Posted by Felix Knecht <fe...@apache.org>.
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 dedicated (empty) local repository that you can then zip/tar.gz.
> You could upload that archive (zip/tar.gz file) on people.apache.org
and unarchive it to the final location from there.
>
> WDYT?
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.
Regards
Felix
Re: Considering the Nexus repository infrastructure for our future releases?
Posted by Pierre-Arnaud Marcelot <pa...@marcelot.net>.
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 zip/tar.gz.
You could upload that archive (zip/tar.gz file) on people.apache.org and unarchive it to the final location from there.
WDYT?
Regards,
Pierre-Arnaud
On 11 mars 2010, at 21:04, Felix Knecht wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 03/11/10 18:41, 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.
>> 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 the "Releasing A Maven Project" Guide [1].
>>
>> I think we've reach the limit with deployments on people.apache.org... My last deployment of Studio for version 1.5.2 took more than four hours (!!).
>>
>> I talked with Chris Custine on that subject and we would probably have a much better performance with Nexus. It also have pretty neat features like stagging that would allow us to upload artifacts and approve (or deny) them later, which could be interesting when voting a release.
>>
>> However, there's seem to be one "drawback" in the fact that once the project is moved to Nexus, deployment on people.apache.org are disabled. All deployments must be done on Nexus.
>> More information on this on this at INFRA-1896 [2].
>>
>> I would really like that we discuss that all together and maybe we could launch a vote to move to Nexus after this discussion.
>>
>> WDYT?
>
> I think that's the way to go. Does there also exists a possibility to
> deploy at least generated release documentation?
>
> Felix
>
>>
>> Thanks,
>> Pierre-Arnaud
>>
>>
>> [1] - http://maven.apache.org/developers/release/apache-release.html
>> [2] - https://issues.apache.org/jira/browse/INFRA-1896
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.14 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAkuZTOsACgkQ2lZVCB08qHExdACgrH6QmuFnTht0S7y4eaXweQxW
> tfkAoKV7bhdyTmuyV6zImFjLXmaCC4e7
> =pew2
> -----END PGP SIGNATURE-----
Re: Considering the Nexus repository infrastructure for our future
releases?
Posted by Felix Knecht <fe...@apache.org>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 03/11/10 18:41, 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.
> 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 the "Releasing A Maven Project" Guide [1].
>
> I think we've reach the limit with deployments on people.apache.org... My last deployment of Studio for version 1.5.2 took more than four hours (!!).
>
> I talked with Chris Custine on that subject and we would probably have a much better performance with Nexus. It also have pretty neat features like stagging that would allow us to upload artifacts and approve (or deny) them later, which could be interesting when voting a release.
>
> However, there's seem to be one "drawback" in the fact that once the project is moved to Nexus, deployment on people.apache.org are disabled. All deployments must be done on Nexus.
> More information on this on this at INFRA-1896 [2].
>
> I would really like that we discuss that all together and maybe we could launch a vote to move to Nexus after this discussion.
>
> WDYT?
I think that's the way to go. Does there also exists a possibility to
deploy at least generated release documentation?
Felix
>
> Thanks,
> Pierre-Arnaud
>
>
> [1] - http://maven.apache.org/developers/release/apache-release.html
> [2] - https://issues.apache.org/jira/browse/INFRA-1896
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkuZTOsACgkQ2lZVCB08qHExdACgrH6QmuFnTht0S7y4eaXweQxW
tfkAoKV7bhdyTmuyV6zImFjLXmaCC4e7
=pew2
-----END PGP SIGNATURE-----
Re: [VOTE] Switching to Apache's Nexus repository infrastructure for next releases of the Directory project
Posted by Pierre-Arnaud Marcelot <pa...@marcelot.net>.
> [X] +1 - Let's switch to Apache's Nexus repository infrastructure for the next releases of the Directory project
Re: [VOTE] Switching to Apache's Nexus repository infrastructure for
next releases of the Directory project
Posted by Kiran Ayyagari <ay...@gmail.com>.
> [ X ] +1 - Let's switch to Apache's Nexus repository infrastructure for the next releases of the Directory project
have seen it at work last year, think we should give it a try
Kiran Ayyagari
Re: [VOTE][RESULTS] Switching to Apache's Nexus repository infrastructure for next releases of the Directory project
Posted by Pierre-Arnaud Marcelot <pa...@marcelot.net>.
Thanks Chris,
These are links I came across when evaluating the move to Nexus.
Let me add another one (pretty similar to the Felix release management process):
http://maven.apache.org/developers/release/apache-release.html
This link is the recommended path for releasing Maven based projects at Apache.
Regards,
Pierre-Arnaud
On 29 mars 2010, at 21:38, Chris Custine wrote:
> Just realized I didn't send the link with the release vote and verification scripts.
>
> http://markmail.org/thread/dobcq3pajdlr2h2s
>
> Chris
> --
> Chris Custine
> FUSESource :: http://fusesource.com
> My Blog :: http://blog.organicelement.com
> Apache ServiceMix :: http://servicemix.apache.org
> Apache Felix :: http://felix.apache.org
> Apache Directory Server :: http://directory.apache.org
>
>
> On Mon, Mar 29, 2010 at 9:59 AM, Chris Custine <ch...@gmail.com> wrote:
> Hi Guys,
> We are using Nexus Staging for Felix and ServiceMix (have been for about 6 months) so I have attached some links below that might help. FWIW, this really simplifies staging, voting, and moving to maven central to the point where its a no-brainer. You won't be disappointed!
>
> http://felix.apache.org/site/release-management-nexus.html
> http://www.sonatype.com/books/nexus-book/reference/staging.html
>
> Also, we have developed a script to download the numbered staging repo and verify signatures etc, of the artifacts. You should check out this recent vote email for Karaf for the svn link to the staging script, and then you can modify it to suit you. BTW, one thing people overlook is that since the staging repo is a full maven repo with just your release artifacts in it, you can add it to your settings.xml or a test project and try to use it in a project, just make sure you use a temporary maven.repo.local setting or clea out your default repo if you cancel the build and stage another vote!
>
> Hope this helps!
> Chris
>
> --
> Chris Custine
> FUSESource :: http://fusesource.com
> My Blog :: http://blog.organicelement.com
> Apache ServiceMix :: http://servicemix.apache.org
> Apache Felix :: http://felix.apache.org
>
> Apache Directory Server :: http://directory.apache.org
>
>
> On Mon, Mar 29, 2010 at 9:29 AM, Alex Karasulu <ak...@gmail.com> wrote:
> Hi Pierre,
>
> On Mon, Mar 29, 2010 at 3:11 PM, Pierre-Arnaud Marcelot <pa...@marcelot.net> wrote:
> Hi,
>
> Just to let you know that I did a little test this morning.
>
> I deployed artifacts from a testing project with multiple sub-projects.
> Everything went fine and I was able to deploy the artifacts on Nexus.
> Once on Nexus, I had the choice to drop the deployed artifacts or promote them to the main repository.
> I dropped them since they were only here for testing purposes.
>
> We are currenlty finishing the work on the 1.5.3 release of Studio and will probably be ready to propose a vote today.
> We will use the Nexus for voting this release and we'll update the release documentation once the process is completely validated.
>
>
> Is there some documentation in existence for this and/or can we update our deployment wiki page to show people how to deploy using nexus. If anything maybe we can add a link etc. Just asking cuz I want to be able to use this later but don't have the brain cycles now to figure it out.
>
> Regards,
> Alex
>
> On 29 mars 2010, at 09:36, Pierre-Arnaud Marcelot wrote:
>
> > Hi,
> >
> > The Jira issue has been resolved.
> >
> > Now, we NEED to deploy everything using Nexus and DO NOT deploy anything at the old location on people.apache.org.
> >
> > Thanks,
> > Pierre-Arnaud
> >
> >
> > On 26 mars 2010, at 10:19, Pierre-Arnaud Marcelot wrote:
> >
> >> FYI, now that Apache DS is released, I opened a Jira for our move to Nexus.
> >>
> >> https://issues.apache.org/jira/browse/INFRA-2574
> >>
> >> Regards,
> >> Pierre-Arnaud
> >>
> >>
> >> On 16 mars 2010, at 11:12, Pierre-Arnaud Marcelot wrote:
> >>
> >>> The vote has been approved.
> >>>
> >>> Here are the results:
> >>>
> >>> 5 +1 votes:
> >>> - Felix Knecht
> >>> - Emmanuel Lécharny
> >>> - Kiran Ayyagari
> >>> - Pierre-Arnaud Marcelot
> >>> - Stefan Seelmann
> >>>
> >>> 1 ±0 abstention vote:
> >>> - Alex Karasulu
> >>>
> >>> No -1 vote.
> >>>
> >>>
> >>> The next step in the process to move to the Nexus infrastructure is now to create a Jira as sub-task of INFRA-1896 [1].
> >>>
> >>> Shall I wait for the ongoing vote of the release of Apache DS 1.5.6 to be closed and the artifacts released before asking to move to Nexus ?
> >>> WDYT ?
> >>>
> >>> Regards,
> >>> Pierre-Arnaud
> >>>
> >>> [1] - https://issues.apache.org/jira/browse/INFRA-1896
> >>>
> >>>
> >>>
> >>> On 12 mars 2010, at 13:32, Pierre-Arnaud Marcelot wrote:
> >>>
> >>>> Hi Stefan and Emmanuel,
> >>>>
> >>>> As you've started to +1 the idea, maybe it would be better to start a real formal vote.
> >>>>
> >>>> So here it is.
> >>>>
> >>>> [ ] +1 - Let's switch to Apache's Nexus repository infrastructure for the next releases of the Directory project
> >>>> [ ] ±0 - Abstain
> >>>> [ ] -1 - Let's keep our current deployment mechanism on people.apache.org
> >>>>
> >>>> Vote is opened for 72 hours.
> >>>>
> >>>> Thanks,
> >>>> Pierre-Arnaud
> >>>>
> >>>>
> >>>> On 12 mars 2010, at 07:45, Stefan Seelmann wrote:
> >>>>
> >>>>> I use Nexus in my current project as repository and it works very well.
> >>>>> So my +1 for that step.
> >>>>>
> >>>>> Kind Regards,
> >>>>> Stefan
> >>>>
> >>>>
> >>>> On 12 mars 2010, at 09:38, Emmanuel Lecharny wrote:
> >>>>
> >>>>> +1 too. If it offers a better support for our releases, I don't see why we should not switch.
> >>>>
> >>>
> >>
> >
>
>
>
>
> --
> Alex Karasulu
> My Blog :: http://www.jroller.com/akarasulu/
> Apache Directory Server :: http://directory.apache.org
> Apache MINA :: http://mina.apache.org
> To set up a meeting with me: http://tungle.me/AlexKarasulu
>
>
Re: [VOTE][RESULTS] Switching to Apache's Nexus repository
infrastructure for next releases of the Directory project
Posted by Chris Custine <ch...@gmail.com>.
Just realized I didn't send the link with the release vote and verification
scripts.
http://markmail.org/thread/dobcq3pajdlr2h2s
<http://markmail.org/thread/dobcq3pajdlr2h2s>Chris
--
Chris Custine
FUSESource :: http://fusesource.com
My Blog :: http://blog.organicelement.com
Apache ServiceMix :: http://servicemix.apache.org
Apache Felix :: http://felix.apache.org
Apache Directory Server :: http://directory.apache.org
On Mon, Mar 29, 2010 at 9:59 AM, Chris Custine <ch...@gmail.com>wrote:
> Hi Guys,
> We are using Nexus Staging for Felix and ServiceMix (have been for about 6
> months) so I have attached some links below that might help. FWIW, this
> really simplifies staging, voting, and moving to maven central to the point
> where its a no-brainer. You won't be disappointed!
>
> http://felix.apache.org/site/release-management-nexus.html
> http://www.sonatype.com/books/nexus-book/reference/staging.html
>
> Also, we have developed a script to download the numbered staging repo and
> verify signatures etc, of the artifacts. You should check out this recent
> vote email for Karaf for the svn link to the staging script, and then you
> can modify it to suit you. BTW, one thing people overlook is that since the
> staging repo is a full maven repo with just your release artifacts in it,
> you can add it to your settings.xml or a test project and try to use it in a
> project, just make sure you use a temporary maven.repo.local setting or clea
> out your default repo if you cancel the build and stage another vote!
>
> Hope this helps!
> Chris
> <http://www.sonatype.com/books/nexus-book/reference/staging.html>
> --
> Chris Custine
> FUSESource :: http://fusesource.com
> My Blog :: http://blog.organicelement.com
> Apache ServiceMix :: http://servicemix.apache.org
> Apache Felix :: http://felix.apache.org
>
> Apache Directory Server :: http://directory.apache.org
>
>
> On Mon, Mar 29, 2010 at 9:29 AM, Alex Karasulu <ak...@gmail.com>wrote:
>
>> Hi Pierre,
>>
>> On Mon, Mar 29, 2010 at 3:11 PM, Pierre-Arnaud Marcelot <pa...@marcelot.net>wrote:
>>
>>> Hi,
>>>
>>> Just to let you know that I did a little test this morning.
>>>
>>> I deployed artifacts from a testing project with multiple sub-projects.
>>> Everything went fine and I was able to deploy the artifacts on Nexus.
>>> Once on Nexus, I had the choice to drop the deployed artifacts or promote
>>> them to the main repository.
>>> I dropped them since they were only here for testing purposes.
>>>
>>> We are currenlty finishing the work on the 1.5.3 release of Studio and
>>> will probably be ready to propose a vote today.
>>> We will use the Nexus for voting this release and we'll update the
>>> release documentation once the process is completely validated.
>>>
>>>
>> Is there some documentation in existence for this and/or can we update our
>> deployment wiki page to show people how to deploy using nexus. If anything
>> maybe we can add a link etc. Just asking cuz I want to be able to use this
>> later but don't have the brain cycles now to figure it out.
>>
>> Regards,
>> Alex
>>
>>
>>> On 29 mars 2010, at 09:36, Pierre-Arnaud Marcelot wrote:
>>>
>>> > Hi,
>>> >
>>> > The Jira issue has been resolved.
>>> >
>>> > Now, we NEED to deploy everything using Nexus and DO NOT deploy
>>> anything at the old location on people.apache.org.
>>> >
>>> > Thanks,
>>> > Pierre-Arnaud
>>> >
>>> >
>>> > On 26 mars 2010, at 10:19, Pierre-Arnaud Marcelot wrote:
>>> >
>>> >> FYI, now that Apache DS is released, I opened a Jira for our move to
>>> Nexus.
>>> >>
>>> >> https://issues.apache.org/jira/browse/INFRA-2574
>>> >>
>>> >> Regards,
>>> >> Pierre-Arnaud
>>> >>
>>> >>
>>> >> On 16 mars 2010, at 11:12, Pierre-Arnaud Marcelot wrote:
>>> >>
>>> >>> The vote has been approved.
>>> >>>
>>> >>> Here are the results:
>>> >>>
>>> >>> 5 +1 votes:
>>> >>> - Felix Knecht
>>> >>> - Emmanuel Lécharny
>>> >>> - Kiran Ayyagari
>>> >>> - Pierre-Arnaud Marcelot
>>> >>> - Stefan Seelmann
>>> >>>
>>> >>> 1 ±0 abstention vote:
>>> >>> - Alex Karasulu
>>> >>>
>>> >>> No -1 vote.
>>> >>>
>>> >>>
>>> >>> The next step in the process to move to the Nexus infrastructure is
>>> now to create a Jira as sub-task of INFRA-1896 [1].
>>> >>>
>>> >>> Shall I wait for the ongoing vote of the release of Apache DS 1.5.6
>>> to be closed and the artifacts released before asking to move to Nexus ?
>>> >>> WDYT ?
>>> >>>
>>> >>> Regards,
>>> >>> Pierre-Arnaud
>>> >>>
>>> >>> [1] - https://issues.apache.org/jira/browse/INFRA-1896
>>> >>>
>>> >>>
>>> >>>
>>> >>> On 12 mars 2010, at 13:32, Pierre-Arnaud Marcelot wrote:
>>> >>>
>>> >>>> Hi Stefan and Emmanuel,
>>> >>>>
>>> >>>> As you've started to +1 the idea, maybe it would be better to start
>>> a real formal vote.
>>> >>>>
>>> >>>> So here it is.
>>> >>>>
>>> >>>> [ ] +1 - Let's switch to Apache's Nexus repository infrastructure
>>> for the next releases of the Directory project
>>> >>>> [ ] ±0 - Abstain
>>> >>>> [ ] -1 - Let's keep our current deployment mechanism on
>>> people.apache.org
>>> >>>>
>>> >>>> Vote is opened for 72 hours.
>>> >>>>
>>> >>>> Thanks,
>>> >>>> Pierre-Arnaud
>>> >>>>
>>> >>>>
>>> >>>> On 12 mars 2010, at 07:45, Stefan Seelmann wrote:
>>> >>>>
>>> >>>>> I use Nexus in my current project as repository and it works very
>>> well.
>>> >>>>> So my +1 for that step.
>>> >>>>>
>>> >>>>> Kind Regards,
>>> >>>>> Stefan
>>> >>>>
>>> >>>>
>>> >>>> On 12 mars 2010, at 09:38, Emmanuel Lecharny wrote:
>>> >>>>
>>> >>>>> +1 too. If it offers a better support for our releases, I don't see
>>> why we should not switch.
>>> >>>>
>>> >>>
>>> >>
>>> >
>>>
>>>
>>
>>
>> --
>> Alex Karasulu
>> My Blog :: http://www.jroller.com/akarasulu/
>> Apache Directory Server :: http://directory.apache.org
>> Apache MINA :: http://mina.apache.org
>> To set up a meeting with me: http://tungle.me/AlexKarasulu
>>
>
>
Re: [VOTE][RESULTS] Switching to Apache's Nexus repository
infrastructure for next releases of the Directory project
Posted by Chris Custine <ch...@gmail.com>.
Hi Guys,
We are using Nexus Staging for Felix and ServiceMix (have been for about 6
months) so I have attached some links below that might help. FWIW, this
really simplifies staging, voting, and moving to maven central to the point
where its a no-brainer. You won't be disappointed!
http://felix.apache.org/site/release-management-nexus.html
http://www.sonatype.com/books/nexus-book/reference/staging.html
Also, we have developed a script to download the numbered staging repo and
verify signatures etc, of the artifacts. You should check out this recent
vote email for Karaf for the svn link to the staging script, and then you
can modify it to suit you. BTW, one thing people overlook is that since the
staging repo is a full maven repo with just your release artifacts in it,
you can add it to your settings.xml or a test project and try to use it in a
project, just make sure you use a temporary maven.repo.local setting or clea
out your default repo if you cancel the build and stage another vote!
Hope this helps!
Chris
<http://www.sonatype.com/books/nexus-book/reference/staging.html>
--
Chris Custine
FUSESource :: http://fusesource.com
My Blog :: http://blog.organicelement.com
Apache ServiceMix :: http://servicemix.apache.org
Apache Felix :: http://felix.apache.org
Apache Directory Server :: http://directory.apache.org
On Mon, Mar 29, 2010 at 9:29 AM, Alex Karasulu <ak...@gmail.com> wrote:
> Hi Pierre,
>
> On Mon, Mar 29, 2010 at 3:11 PM, Pierre-Arnaud Marcelot <pa...@marcelot.net>wrote:
>
>> Hi,
>>
>> Just to let you know that I did a little test this morning.
>>
>> I deployed artifacts from a testing project with multiple sub-projects.
>> Everything went fine and I was able to deploy the artifacts on Nexus.
>> Once on Nexus, I had the choice to drop the deployed artifacts or promote
>> them to the main repository.
>> I dropped them since they were only here for testing purposes.
>>
>> We are currenlty finishing the work on the 1.5.3 release of Studio and
>> will probably be ready to propose a vote today.
>> We will use the Nexus for voting this release and we'll update the release
>> documentation once the process is completely validated.
>>
>>
> Is there some documentation in existence for this and/or can we update our
> deployment wiki page to show people how to deploy using nexus. If anything
> maybe we can add a link etc. Just asking cuz I want to be able to use this
> later but don't have the brain cycles now to figure it out.
>
> Regards,
> Alex
>
>
>> On 29 mars 2010, at 09:36, Pierre-Arnaud Marcelot wrote:
>>
>> > Hi,
>> >
>> > The Jira issue has been resolved.
>> >
>> > Now, we NEED to deploy everything using Nexus and DO NOT deploy anything
>> at the old location on people.apache.org.
>> >
>> > Thanks,
>> > Pierre-Arnaud
>> >
>> >
>> > On 26 mars 2010, at 10:19, Pierre-Arnaud Marcelot wrote:
>> >
>> >> FYI, now that Apache DS is released, I opened a Jira for our move to
>> Nexus.
>> >>
>> >> https://issues.apache.org/jira/browse/INFRA-2574
>> >>
>> >> Regards,
>> >> Pierre-Arnaud
>> >>
>> >>
>> >> On 16 mars 2010, at 11:12, Pierre-Arnaud Marcelot wrote:
>> >>
>> >>> The vote has been approved.
>> >>>
>> >>> Here are the results:
>> >>>
>> >>> 5 +1 votes:
>> >>> - Felix Knecht
>> >>> - Emmanuel Lécharny
>> >>> - Kiran Ayyagari
>> >>> - Pierre-Arnaud Marcelot
>> >>> - Stefan Seelmann
>> >>>
>> >>> 1 ±0 abstention vote:
>> >>> - Alex Karasulu
>> >>>
>> >>> No -1 vote.
>> >>>
>> >>>
>> >>> The next step in the process to move to the Nexus infrastructure is
>> now to create a Jira as sub-task of INFRA-1896 [1].
>> >>>
>> >>> Shall I wait for the ongoing vote of the release of Apache DS 1.5.6 to
>> be closed and the artifacts released before asking to move to Nexus ?
>> >>> WDYT ?
>> >>>
>> >>> Regards,
>> >>> Pierre-Arnaud
>> >>>
>> >>> [1] - https://issues.apache.org/jira/browse/INFRA-1896
>> >>>
>> >>>
>> >>>
>> >>> On 12 mars 2010, at 13:32, Pierre-Arnaud Marcelot wrote:
>> >>>
>> >>>> Hi Stefan and Emmanuel,
>> >>>>
>> >>>> As you've started to +1 the idea, maybe it would be better to start a
>> real formal vote.
>> >>>>
>> >>>> So here it is.
>> >>>>
>> >>>> [ ] +1 - Let's switch to Apache's Nexus repository infrastructure for
>> the next releases of the Directory project
>> >>>> [ ] ±0 - Abstain
>> >>>> [ ] -1 - Let's keep our current deployment mechanism on
>> people.apache.org
>> >>>>
>> >>>> Vote is opened for 72 hours.
>> >>>>
>> >>>> Thanks,
>> >>>> Pierre-Arnaud
>> >>>>
>> >>>>
>> >>>> On 12 mars 2010, at 07:45, Stefan Seelmann wrote:
>> >>>>
>> >>>>> I use Nexus in my current project as repository and it works very
>> well.
>> >>>>> So my +1 for that step.
>> >>>>>
>> >>>>> Kind Regards,
>> >>>>> Stefan
>> >>>>
>> >>>>
>> >>>> On 12 mars 2010, at 09:38, Emmanuel Lecharny wrote:
>> >>>>
>> >>>>> +1 too. If it offers a better support for our releases, I don't see
>> why we should not switch.
>> >>>>
>> >>>
>> >>
>> >
>>
>>
>
>
> --
> Alex Karasulu
> My Blog :: http://www.jroller.com/akarasulu/
> Apache Directory Server :: http://directory.apache.org
> Apache MINA :: http://mina.apache.org
> To set up a meeting with me: http://tungle.me/AlexKarasulu
>
Re: [VOTE][RESULTS] Switching to Apache's Nexus repository
infrastructure for next releases of the Directory project
Posted by Alex Karasulu <ak...@gmail.com>.
Hi Pierre,
On Mon, Mar 29, 2010 at 3:11 PM, Pierre-Arnaud Marcelot <pa...@marcelot.net>wrote:
> Hi,
>
> Just to let you know that I did a little test this morning.
>
> I deployed artifacts from a testing project with multiple sub-projects.
> Everything went fine and I was able to deploy the artifacts on Nexus.
> Once on Nexus, I had the choice to drop the deployed artifacts or promote
> them to the main repository.
> I dropped them since they were only here for testing purposes.
>
> We are currenlty finishing the work on the 1.5.3 release of Studio and will
> probably be ready to propose a vote today.
> We will use the Nexus for voting this release and we'll update the release
> documentation once the process is completely validated.
>
>
Is there some documentation in existence for this and/or can we update our
deployment wiki page to show people how to deploy using nexus. If anything
maybe we can add a link etc. Just asking cuz I want to be able to use this
later but don't have the brain cycles now to figure it out.
Regards,
Alex
> On 29 mars 2010, at 09:36, Pierre-Arnaud Marcelot wrote:
>
> > Hi,
> >
> > The Jira issue has been resolved.
> >
> > Now, we NEED to deploy everything using Nexus and DO NOT deploy anything
> at the old location on people.apache.org.
> >
> > Thanks,
> > Pierre-Arnaud
> >
> >
> > On 26 mars 2010, at 10:19, Pierre-Arnaud Marcelot wrote:
> >
> >> FYI, now that Apache DS is released, I opened a Jira for our move to
> Nexus.
> >>
> >> https://issues.apache.org/jira/browse/INFRA-2574
> >>
> >> Regards,
> >> Pierre-Arnaud
> >>
> >>
> >> On 16 mars 2010, at 11:12, Pierre-Arnaud Marcelot wrote:
> >>
> >>> The vote has been approved.
> >>>
> >>> Here are the results:
> >>>
> >>> 5 +1 votes:
> >>> - Felix Knecht
> >>> - Emmanuel Lécharny
> >>> - Kiran Ayyagari
> >>> - Pierre-Arnaud Marcelot
> >>> - Stefan Seelmann
> >>>
> >>> 1 ±0 abstention vote:
> >>> - Alex Karasulu
> >>>
> >>> No -1 vote.
> >>>
> >>>
> >>> The next step in the process to move to the Nexus infrastructure is now
> to create a Jira as sub-task of INFRA-1896 [1].
> >>>
> >>> Shall I wait for the ongoing vote of the release of Apache DS 1.5.6 to
> be closed and the artifacts released before asking to move to Nexus ?
> >>> WDYT ?
> >>>
> >>> Regards,
> >>> Pierre-Arnaud
> >>>
> >>> [1] - https://issues.apache.org/jira/browse/INFRA-1896
> >>>
> >>>
> >>>
> >>> On 12 mars 2010, at 13:32, Pierre-Arnaud Marcelot wrote:
> >>>
> >>>> Hi Stefan and Emmanuel,
> >>>>
> >>>> As you've started to +1 the idea, maybe it would be better to start a
> real formal vote.
> >>>>
> >>>> So here it is.
> >>>>
> >>>> [ ] +1 - Let's switch to Apache's Nexus repository infrastructure for
> the next releases of the Directory project
> >>>> [ ] ±0 - Abstain
> >>>> [ ] -1 - Let's keep our current deployment mechanism on
> people.apache.org
> >>>>
> >>>> Vote is opened for 72 hours.
> >>>>
> >>>> Thanks,
> >>>> Pierre-Arnaud
> >>>>
> >>>>
> >>>> On 12 mars 2010, at 07:45, Stefan Seelmann wrote:
> >>>>
> >>>>> I use Nexus in my current project as repository and it works very
> well.
> >>>>> So my +1 for that step.
> >>>>>
> >>>>> Kind Regards,
> >>>>> Stefan
> >>>>
> >>>>
> >>>> On 12 mars 2010, at 09:38, Emmanuel Lecharny wrote:
> >>>>
> >>>>> +1 too. If it offers a better support for our releases, I don't see
> why we should not switch.
> >>>>
> >>>
> >>
> >
>
>
--
Alex Karasulu
My Blog :: http://www.jroller.com/akarasulu/
Apache Directory Server :: http://directory.apache.org
Apache MINA :: http://mina.apache.org
To set up a meeting with me: http://tungle.me/AlexKarasulu
Re: [VOTE][RESULTS] Switching to Apache's Nexus repository infrastructure for next releases of the Directory project
Posted by Pierre-Arnaud Marcelot <pa...@marcelot.net>.
Hi,
Just to let you know that I did a little test this morning.
I deployed artifacts from a testing project with multiple sub-projects.
Everything went fine and I was able to deploy the artifacts on Nexus.
Once on Nexus, I had the choice to drop the deployed artifacts or promote them to the main repository.
I dropped them since they were only here for testing purposes.
We are currenlty finishing the work on the 1.5.3 release of Studio and will probably be ready to propose a vote today.
We will use the Nexus for voting this release and we'll update the release documentation once the process is completely validated.
Regards,
Pierre-Arnaud
On 29 mars 2010, at 09:36, Pierre-Arnaud Marcelot wrote:
> Hi,
>
> The Jira issue has been resolved.
>
> Now, we NEED to deploy everything using Nexus and DO NOT deploy anything at the old location on people.apache.org.
>
> Thanks,
> Pierre-Arnaud
>
>
> On 26 mars 2010, at 10:19, Pierre-Arnaud Marcelot wrote:
>
>> FYI, now that Apache DS is released, I opened a Jira for our move to Nexus.
>>
>> https://issues.apache.org/jira/browse/INFRA-2574
>>
>> Regards,
>> Pierre-Arnaud
>>
>>
>> On 16 mars 2010, at 11:12, Pierre-Arnaud Marcelot wrote:
>>
>>> The vote has been approved.
>>>
>>> Here are the results:
>>>
>>> 5 +1 votes:
>>> - Felix Knecht
>>> - Emmanuel Lécharny
>>> - Kiran Ayyagari
>>> - Pierre-Arnaud Marcelot
>>> - Stefan Seelmann
>>>
>>> 1 ±0 abstention vote:
>>> - Alex Karasulu
>>>
>>> No -1 vote.
>>>
>>>
>>> The next step in the process to move to the Nexus infrastructure is now to create a Jira as sub-task of INFRA-1896 [1].
>>>
>>> Shall I wait for the ongoing vote of the release of Apache DS 1.5.6 to be closed and the artifacts released before asking to move to Nexus ?
>>> WDYT ?
>>>
>>> Regards,
>>> Pierre-Arnaud
>>>
>>> [1] - https://issues.apache.org/jira/browse/INFRA-1896
>>>
>>>
>>>
>>> On 12 mars 2010, at 13:32, Pierre-Arnaud Marcelot wrote:
>>>
>>>> Hi Stefan and Emmanuel,
>>>>
>>>> As you've started to +1 the idea, maybe it would be better to start a real formal vote.
>>>>
>>>> So here it is.
>>>>
>>>> [ ] +1 - Let's switch to Apache's Nexus repository infrastructure for the next releases of the Directory project
>>>> [ ] ±0 - Abstain
>>>> [ ] -1 - Let's keep our current deployment mechanism on people.apache.org
>>>>
>>>> Vote is opened for 72 hours.
>>>>
>>>> Thanks,
>>>> Pierre-Arnaud
>>>>
>>>>
>>>> On 12 mars 2010, at 07:45, Stefan Seelmann wrote:
>>>>
>>>>> I use Nexus in my current project as repository and it works very well.
>>>>> So my +1 for that step.
>>>>>
>>>>> Kind Regards,
>>>>> Stefan
>>>>
>>>>
>>>> On 12 mars 2010, at 09:38, Emmanuel Lecharny wrote:
>>>>
>>>>> +1 too. If it offers a better support for our releases, I don't see why we should not switch.
>>>>
>>>
>>
>
Re: [VOTE][RESULTS] Switching to Apache's Nexus repository infrastructure for next releases of the Directory project
Posted by Pierre-Arnaud Marcelot <pa...@marcelot.net>.
Hi,
The Jira issue has been resolved.
Now, we NEED to deploy everything using Nexus and DO NOT deploy anything at the old location on people.apache.org.
Thanks,
Pierre-Arnaud
On 26 mars 2010, at 10:19, Pierre-Arnaud Marcelot wrote:
> FYI, now that Apache DS is released, I opened a Jira for our move to Nexus.
>
> https://issues.apache.org/jira/browse/INFRA-2574
>
> Regards,
> Pierre-Arnaud
>
>
> On 16 mars 2010, at 11:12, Pierre-Arnaud Marcelot wrote:
>
>> The vote has been approved.
>>
>> Here are the results:
>>
>> 5 +1 votes:
>> - Felix Knecht
>> - Emmanuel Lécharny
>> - Kiran Ayyagari
>> - Pierre-Arnaud Marcelot
>> - Stefan Seelmann
>>
>> 1 ±0 abstention vote:
>> - Alex Karasulu
>>
>> No -1 vote.
>>
>>
>> The next step in the process to move to the Nexus infrastructure is now to create a Jira as sub-task of INFRA-1896 [1].
>>
>> Shall I wait for the ongoing vote of the release of Apache DS 1.5.6 to be closed and the artifacts released before asking to move to Nexus ?
>> WDYT ?
>>
>> Regards,
>> Pierre-Arnaud
>>
>> [1] - https://issues.apache.org/jira/browse/INFRA-1896
>>
>>
>>
>> On 12 mars 2010, at 13:32, Pierre-Arnaud Marcelot wrote:
>>
>>> Hi Stefan and Emmanuel,
>>>
>>> As you've started to +1 the idea, maybe it would be better to start a real formal vote.
>>>
>>> So here it is.
>>>
>>> [ ] +1 - Let's switch to Apache's Nexus repository infrastructure for the next releases of the Directory project
>>> [ ] ±0 - Abstain
>>> [ ] -1 - Let's keep our current deployment mechanism on people.apache.org
>>>
>>> Vote is opened for 72 hours.
>>>
>>> Thanks,
>>> Pierre-Arnaud
>>>
>>>
>>> On 12 mars 2010, at 07:45, Stefan Seelmann wrote:
>>>
>>>> I use Nexus in my current project as repository and it works very well.
>>>> So my +1 for that step.
>>>>
>>>> Kind Regards,
>>>> Stefan
>>>
>>>
>>> On 12 mars 2010, at 09:38, Emmanuel Lecharny wrote:
>>>
>>>> +1 too. If it offers a better support for our releases, I don't see why we should not switch.
>>>
>>
>
Re: [VOTE][RESULTS] Switching to Apache's Nexus repository infrastructure for next releases of the Directory project
Posted by Pierre-Arnaud Marcelot <pa...@marcelot.net>.
FYI, now that Apache DS is released, I opened a Jira for our move to Nexus.
https://issues.apache.org/jira/browse/INFRA-2574
Regards,
Pierre-Arnaud
On 16 mars 2010, at 11:12, Pierre-Arnaud Marcelot wrote:
> The vote has been approved.
>
> Here are the results:
>
> 5 +1 votes:
> - Felix Knecht
> - Emmanuel Lécharny
> - Kiran Ayyagari
> - Pierre-Arnaud Marcelot
> - Stefan Seelmann
>
> 1 ±0 abstention vote:
> - Alex Karasulu
>
> No -1 vote.
>
>
> The next step in the process to move to the Nexus infrastructure is now to create a Jira as sub-task of INFRA-1896 [1].
>
> Shall I wait for the ongoing vote of the release of Apache DS 1.5.6 to be closed and the artifacts released before asking to move to Nexus ?
> WDYT ?
>
> Regards,
> Pierre-Arnaud
>
> [1] - https://issues.apache.org/jira/browse/INFRA-1896
>
>
>
> On 12 mars 2010, at 13:32, Pierre-Arnaud Marcelot wrote:
>
>> Hi Stefan and Emmanuel,
>>
>> As you've started to +1 the idea, maybe it would be better to start a real formal vote.
>>
>> So here it is.
>>
>> [ ] +1 - Let's switch to Apache's Nexus repository infrastructure for the next releases of the Directory project
>> [ ] ±0 - Abstain
>> [ ] -1 - Let's keep our current deployment mechanism on people.apache.org
>>
>> Vote is opened for 72 hours.
>>
>> Thanks,
>> Pierre-Arnaud
>>
>>
>> On 12 mars 2010, at 07:45, Stefan Seelmann wrote:
>>
>>> I use Nexus in my current project as repository and it works very well.
>>> So my +1 for that step.
>>>
>>> Kind Regards,
>>> Stefan
>>
>>
>> On 12 mars 2010, at 09:38, Emmanuel Lecharny wrote:
>>
>>> +1 too. If it offers a better support for our releases, I don't see why we should not switch.
>>
>
[VOTE][RESULTS] Switching to Apache's Nexus repository infrastructure for next releases of the Directory project
Posted by Pierre-Arnaud Marcelot <pa...@marcelot.net>.
The vote has been approved.
Here are the results:
5 +1 votes:
- Felix Knecht
- Emmanuel Lécharny
- Kiran Ayyagari
- Pierre-Arnaud Marcelot
- Stefan Seelmann
1 ±0 abstention vote:
- Alex Karasulu
No -1 vote.
The next step in the process to move to the Nexus infrastructure is now to create a Jira as sub-task of INFRA-1896 [1].
Shall I wait for the ongoing vote of the release of Apache DS 1.5.6 to be closed and the artifacts released before asking to move to Nexus ?
WDYT ?
Regards,
Pierre-Arnaud
[1] - https://issues.apache.org/jira/browse/INFRA-1896
On 12 mars 2010, at 13:32, Pierre-Arnaud Marcelot wrote:
> Hi Stefan and Emmanuel,
>
> As you've started to +1 the idea, maybe it would be better to start a real formal vote.
>
> So here it is.
>
> [ ] +1 - Let's switch to Apache's Nexus repository infrastructure for the next releases of the Directory project
> [ ] ±0 - Abstain
> [ ] -1 - Let's keep our current deployment mechanism on people.apache.org
>
> Vote is opened for 72 hours.
>
> Thanks,
> Pierre-Arnaud
>
>
> On 12 mars 2010, at 07:45, Stefan Seelmann wrote:
>
>> I use Nexus in my current project as repository and it works very well.
>> So my +1 for that step.
>>
>> Kind Regards,
>> Stefan
>
>
> On 12 mars 2010, at 09:38, Emmanuel Lecharny wrote:
>
>> +1 too. If it offers a better support for our releases, I don't see why we should not switch.
>
Re: [VOTE] Switching to Apache's Nexus repository infrastructure
for next releases of the Directory project
Posted by Emmanuel Lecharny <el...@gmail.com>.
On 3/12/10 1:32 PM, Pierre-Arnaud Marcelot wrote:
> Hi Stefan and Emmanuel,
>
> As you've started to +1 the idea, maybe it would be better to start a real formal vote.
>
> So here it is.
>
> [X] +1 - Let's switch to Apache's Nexus repository infrastructure for the next releases of the Directory project
>
--
Regards,
Cordialement,
Emmanuel Lécharny
www.nextury.com
Re: [VOTE] Switching to Apache's Nexus repository infrastructure for
next releases of the Directory project
Posted by Alex Karasulu <ak...@gmail.com>.
On Fri, Mar 12, 2010 at 2:32 PM, Pierre-Arnaud Marcelot <pa...@marcelot.net> wrote:
> [ ] +1 - Let's switch to Apache's Nexus repository infrastructure for the next releases of the Directory project
> [ X ] ±0 - Abstain
> [ ] -1 - Let's keep our current deployment mechanism on people.apache.org
--
Alex Karasulu
My Blog :: http://www.jroller.com/akarasulu/
Apache Directory Server :: http://directory.apache.org
Apache MINA :: http://mina.apache.org
Re: [VOTE] Switching to Apache's Nexus repository infrastructure
for next releases of the Directory project
Posted by Felix Knecht <fe...@apache.org>.
[X ] +1 - Let's switch to Apache's Nexus repository infrastructure for
the next releases of the Directory project
Felix
Re: [VOTE] Switching to Apache's Nexus repository infrastructure for next releases of the Directory project
Posted by Pierre-Arnaud Marcelot <pa...@marcelot.net>.
The vote is now closed.
Results will follow.
Regards,
Pierre-Arnaud
On 15 mars 2010, at 11:33, Stefan Seelmann wrote:
>
>> [X] +1 - Let's switch to Apache's Nexus repository infrastructure for the next releases of the Directory project
>
>
Re: [VOTE] Switching to Apache's Nexus repository infrastructure
for next releases of the Directory project
Posted by Stefan Seelmann <se...@apache.org>.
> [X] +1 - Let's switch to Apache's Nexus repository infrastructure for the next releases of the Directory project
[VOTE] Switching to Apache's Nexus repository infrastructure for next releases of the Directory project
Posted by Pierre-Arnaud Marcelot <pa...@marcelot.net>.
Hi Stefan and Emmanuel,
As you've started to +1 the idea, maybe it would be better to start a real formal vote.
So here it is.
[ ] +1 - Let's switch to Apache's Nexus repository infrastructure for the next releases of the Directory project
[ ] ±0 - Abstain
[ ] -1 - Let's keep our current deployment mechanism on people.apache.org
Vote is opened for 72 hours.
Thanks,
Pierre-Arnaud
On 12 mars 2010, at 07:45, Stefan Seelmann wrote:
> I use Nexus in my current project as repository and it works very well.
> So my +1 for that step.
>
> Kind Regards,
> Stefan
On 12 mars 2010, at 09:38, Emmanuel Lecharny wrote:
> +1 too. If it offers a better support for our releases, I don't see why we should not switch.
Re: Considering the Nexus repository infrastructure for our future
releases?
Posted by Emmanuel Lecharny <el...@gmail.com>.
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
www.nextury.com
Re: Considering the Nexus repository infrastructure for our future
releases?
Posted by Stefan Seelmann <se...@apache.org>.
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.
> 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 the "Releasing A Maven Project" Guide [1].
>
> I think we've reach the limit with deployments on people.apache.org... My last deployment of Studio for version 1.5.2 took more than four hours (!!).
>
> I talked with Chris Custine on that subject and we would probably have a much better performance with Nexus. It also have pretty neat features like stagging that would allow us to upload artifacts and approve (or deny) them later, which could be interesting when voting a release.
>
> However, there's seem to be one "drawback" in the fact that once the project is moved to Nexus, deployment on people.apache.org are disabled. All deployments must be done on Nexus.
> More information on this on this at INFRA-1896 [2].
>
> I would really like that we discuss that all together and maybe we could launch a vote to move to Nexus after this discussion.
>
> WDYT?
>
> Thanks,
> Pierre-Arnaud
>
>
> [1] - http://maven.apache.org/developers/release/apache-release.html
> [2] - https://issues.apache.org/jira/browse/INFRA-1896
Re: Considering the Nexus repository infrastructure for our future
releases?
Posted by Jesse McConnell <je...@gmail.com>.
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.mcconnell@gmail.com
On Thu, Mar 11, 2010 at 11:41, Pierre-Arnaud Marcelot <pa...@marcelot.net> wrote:
> 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 the "Releasing A Maven Project" Guide [1].
>
> I think we've reach the limit with deployments on people.apache.org... My last deployment of Studio for version 1.5.2 took more than four hours (!!).
>
> I talked with Chris Custine on that subject and we would probably have a much better performance with Nexus. It also have pretty neat features like stagging that would allow us to upload artifacts and approve (or deny) them later, which could be interesting when voting a release.
>
> However, there's seem to be one "drawback" in the fact that once the project is moved to Nexus, deployment on people.apache.org are disabled. All deployments must be done on Nexus.
> More information on this on this at INFRA-1896 [2].
>
> I would really like that we discuss that all together and maybe we could launch a vote to move to Nexus after this discussion.
>
> WDYT?
>
> Thanks,
> Pierre-Arnaud
>
>
> [1] - http://maven.apache.org/developers/release/apache-release.html
> [2] - https://issues.apache.org/jira/browse/INFRA-1896