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.
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-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
