Made some progress; by adding an 'rc' profile in my maven / settings.xml containing the gpg.passphrase, using commons-parent-12, I'm able to sign the artifacts.
My input is: What is the release version for "Commons JEXL"? (org.apache.commons:commons-jexl) 2.0: : 2.0-RC1 What is SCM release tag or label for "Commons JEXL"? (org.apache.commons:commons-jexl) commons-jexl-2.0: : JEXL_2_0_RC1 What is the new development version for "Commons JEXL"? (org.apache.commons:commons-jexl) 2.1-SNAPSHOT: : 2.0-SNAPSHOT The new pb is related to svn, the svn copy fails: [INFO] Trace org.apache.maven.BuildFailureException: Unable to tag SCM Provider message: The svn tag command failed. Command output: svn: No such revision 836226 With the following trace: [INFO] Tagging release with the label JEXL_2_0_RC1... [INFO] Executing: /bin/sh -c cd /Users/henri/Java/apache-commons/rc1/commons/jexl-2.0 && svn --non-interactive copy --file /var/folders/Ya/YaSJZzgsHu4O4NXovx-nNE+++TI/-Tmp-/maven-scm-1545582656.commit --revision 836226 https://svn.apache.org/repos/asf/commons/proper/jexl/tags/JEXL_2_0_RC1 https://svn.apache.org/repos/asf/commons/proper/jexl/tags/JEXL_2_0_RC1 The source & destination of the svn copy are the same... I suspect the pom.xml should carry somewhere the 'trunk' information; may be the <scm> should mention the trunk rather than RC1 ? Hints welcome. Henrib -- View this message in context: http://old.nabble.com/Help-cutting-JEXL-2.0-RC1-needed-tp26339499p26351941.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
