Am 03.08.2011 07:32, schrieb Henri Yandell:
On Tue, Aug 2, 2011 at 9:30 PM, Phil Steitz<phil.ste...@gmail.com> wrote:
On 8/2/11 5:22 PM, Henri Yandell wrote:
On Tue, Aug 2, 2011 at 7:23 AM, Emmanuel Bourg<ebo...@apache.org> wrote:
Are we still going to deploy Maven artifacts by SCPing to
m2-ibiblio-rsync-repository on people.apache.org?
I've been discussing the permissions issue for the old groupIds on Nexus
with the Infra team (i.e components using the old groupId
commons-<componentname> need a specific configuration on the snapshot and
release repositories).
Brian Demers kindly proposed to allow the deployment of all commons-* groups
on Nexus, but it would require to block the deployment through
people.apache.org to avoid metadata conflicts.
Do we all agree on using exclusively Nexus for our releases?
I would prefer to leave the door open to release more point releases
of [pool] and [dbcp] 1.x using the working scripts that i have, so
pls do not nuke those. The new versions are in the org.apache
groupId tree, so we will have no choice but to use nexus for those.
I will have agree to use nexus for the maven repo bits, but prefer
to create the actual release artifacts locally, examine them, call a
VOTE on them and move the same bits to /dist. Personally, I would
rather see us move back the other way (use the Tomcat setup, with
Ant tasks pushing to p.a.o/rysnch), but I can see I am in the
minority here, so will not stand in the way.
Well, I'm in the same minority and I'm not aware it's a minority (have
we taken a vote from those release managing?).
Nexus, Maven release-plugin, they all fire off my keep-it-simple
warning flags. They mistake magic for simplicity.
I count myself to the same group.
However, for me the most important point is that there is a really
fool-proof description of the release process. Do we already have this
for Nexus?
Oliver
Hen
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
