thanks for the plugin

• However why do you not propose to use SCM conf job for releasing instead of forcing user to declare SCM parameters in the pom.xml ?
• BIG PROBLEM : you tag on the SCM with the job name suffixed by the release number. WHY ? Ex :
  INFO Tagging release with the label test-14-standard-web-1_0_0_0_3...

Instead of tagging my test-14-standard-web with v1_0_0_0_3 as requested in the input release field before the release action.

So because our SCM check the tag syntax the action is rejected

It is not the plugin but maven-release-plugin that is responsible of this

(http://jira.codehaus.org/browse/MRELEASE-159, http://jira.codehaus.org/browse/MRELEASE-150)

but How can I configure it

I must give the -Dtag=v1_0_0_0_3 parameter to release:prepare but it will be fine if M2 release plugin could display on the action page, a input field with the SCM tag (with a default value)

Can I create a issue ?