commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sebb <seb...@gmail.com>
Subject Re: Staging/publishing procedure and tools
Date Tue, 30 Mar 2010 20:02:45 GMT
On 29/03/2010, Niall Pemberton <niall.pemberton@gmail.com> wrote:
> On Mon, Mar 29, 2010 at 4:40 PM, henrib <henrib@apache.org> wrote:
>  >
>  >
>  > I've used the http://wiki.apache.org/commons/CreatingReleases procedure to
>  > release JEXL-2.0 (from Windows, not working on Unix/Mac) and I'm trying to
>  > reuse it for JEXL-2.0.1.
>  >
>  > It appears 'mvn -Prc release:perform...' no longer generates the expected
>  > artefacts.
>  > 'mvn -Prc release:prepare' happily builds commons-jexl-2.0.1-RC1.jar and
>  > tags COMMONS_JEXL_2_0_1-RC1.
>  > 'mvn -Prc release:perform...' insists on creating commons-jexl-2.0.jar
>  > instead of commons-jexl-2.0.1-RC1.jar .
>  > The assembly/{bin,src}.xml seem normal, the pom.xml specifies
>  > <commons.release.version>2.0.1</commons.release.version> and
>  > <commons.rc.version>RC1</commons.rc.version>.
>  > Tried on WinXP & OS X on a fresh m2 repository, same result, no success.
>  >
>  > Am I missing an obvious step / doc / procedure ?
>  > Could this be an undetected "regression" (may be through commons-parent-14)
>  > ?
>  >
>  > IMHO, our community would benefit from finishing the (designed to be)
>  > automated and reliable publishing process described in the Wiki. Especially
>  > since the manual procedures (
>  > http://commons.apache.org/releases/prepare.html and
>  > http://commons.apache.org/releases/release.html ) are complex and appear to
>  > focus on ant / maven-1 projects. This likely would allow faster/smaller
>  > release cycles and more lively projects.
>
>
> IMO you should use the manual process - its not that complex and you
>  would have had far less trouble than all the struggling you've been
>  doing with the release plugin. Also the release plugin only does part
>  of the release process and still leaves a whole load to do manually -
>  so the release plugin isn't really saving you much anyway.
>
>  1. Update the version number to 2.0.1 in the pom.xml and commit the change
>  2. Do a subversion update
>  3. Tag Jexl RC1
>  4. Check out the Jexl RC1 tag
>  5. run "mvn -Prc install" on the RC1 checked out code - this creates
>  artifacts, signs and checksums in your local m2 repo
>  6. run "mvn site" to generate the site (just for review)
>  7. Upload the RC1 artifacts and site for review to your ASF dir on
>  people.apache.org
>  8. Call VOTE
>  9. Copy maven artifacts to
>  http://people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/commons/commons-jexl/2.0.1
>  10. Update maven-metadata.xml  (and re-create md5 & sha1 checksums)

What has to be changed here?

>  The above is just what replaces the maven release plugin - you also
>  need to do the other stuff in the release guide manually whichever way
>  you do it

Does this mean that the "release" profile is no longer needed in the parent pom?

>
>  Niall
>
>
>  > Anyone else also interested by the topic? I'm no maven plugin expert but
>  > will try to help, test and learn if shown the way.
>  > Best regards,
>  > Henrib
>  > --
>  > View this message in context: http://n4.nabble.com/Staging-publishing-procedure-and-tools-tp1695256p1695256.html
>  > Sent from the Commons - Dev mailing list archive at Nabble.com.
>  >
>  > ---------------------------------------------------------------------
>  > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>  > For additional commands, e-mail: dev-help@commons.apache.org
>  >
>  >
>
>  ---------------------------------------------------------------------
>  To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>  For additional commands, e-mail: dev-help@commons.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Mime
View raw message