On Tue, May 25, 2010 at 1:51 PM, Wes Wannemacher <w...@wantii.com> wrote: > On Tue, May 25, 2010 at 10:35 AM, Wendy Smoak <wsm...@gmail.com> wrote: >> On Tue, May 25, 2010 at 10:21 AM, Lukasz Lenart >> <lukasz.len...@googlemail.com> wrote: >> >>> It's is in staging repo but I want to use Nexus for that and waiting >>> for clarification. As I understood I can removed it from the repo and >>> do it again. If not I will call for a Vote. >> >> You're fine, just sort out how to stage it in the new repo and then >> call a vote to release the master pom. :) This is good practice >> learning to stage and promote a single artifact before you try it with >> the whole thing. >> >> -- >> Wendy > > +1 > > This was my motivation for moving to nexus... Martin, sometimes I > think we all get the verb "release" confused.
That was basically my point. At the ASF, a release is a package made available to the general public, and as such it can only be made after a vote by the relevant PMC. I understand that Maven uses the term 'release' to mean something different, but that just means we need to qualify the term when we are talking about a Maven procedure. When Lukasz said he had "made the release", that, at the ASF, will normally be taken to mean an ASF release, which requires a vote. Thus it was an incorrect statement. For someone from another project, or the ASF board, who is not familiar with Maven to drop in here and see that statement and see no corresponding vote, well, that would be bad. So when we mean the Maven thing that they happen to call a release, let's just be explicit that we're talking about the Maven thing. And if we use the term 'release' without qualification, let's use that to refer only to what the ASF calls a release, with a corresponding vote. -- Martin Cooper > On one hand, there is > the logical act of "releasing" our artifacts to the public. On the > other, there is the mechanical act of invoking maven's release plugin. > What Lukasz is referring to is the mechanical act of invoking maven's > release plugin. It will push the artifact to the nexus staging > repository at which point, we can slurp it up and test it (hopefully > by running some test apps). Then, give our vote. This is a bit tricky > though because Lukasz is trying to commit changes that will result in > making nexus integration possible. So, he'll probably have to change > the pom, invoke the maven release plugin, and then check that nexus > received the new artifact in our staging repository. I assume we'll > see a small flurry of svn commits that look like traditional releases > (svn branches, poms having -SNAPSHOT versions removed, etc.). But, > nothing will end up on maven central or in people.a.o/dist until after > we've voted on the quality. > > To answer Lukasz's question, I would assume that the section you > mention does indeed at least need removed. I haven't looked at the > apache parent that we're inheriting from in struts-master, or our > nexus configuration, but IIRC, the reposit...@apache.org team > indicated that inheriting from the parent is all that is necessary. > > I would assume though, that we (anyone who plans to perform a release) > will need to setup our maven settings.xml file to include our LDAP > apache username and password. I would imagine that Nexus is configured > to only allow struts committers to push artifacts into the repository. > (Wendy, correct me if I'm wrong, but) I think usually this is handled > by having a server entry in your settings.xml file that matches up > with the <id /> record in the pom. > > -Wes > > -- > Wes Wannemacher > > Head Engineer, WanTii, Inc. > Need Training? Struts, Spring, Maven, Tomcat... > Ask me for a quote! > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org > For additional commands, e-mail: dev-h...@struts.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
