[ http://jira.codehaus.org/browse/MRELEASE-150?page=comments#action_72321 ] Yuri Schimke commented on MRELEASE-150: ---------------------------------------
Just realised, the default is obviously null, so that it prompts you to enter the label. So its actually set at a point that understands the various versions. Can this be addressed by adding extra variables that can be referenced i.e. - version.previous - version.release - version.next > Can't add prefix to tags without affecting version > -------------------------------------------------- > > Key: MRELEASE-150 > URL: http://jira.codehaus.org/browse/MRELEASE-150 > Project: Maven 2.x Release Plugin > Issue Type: Bug > Affects Versions: 2.0-beta-4 > Reporter: Yuri Schimke > Priority: Minor > > I added the following to my POM > <plugin> > <artifactId>maven-release-plugin</artifactId> > <configuration> > <tag>XXX-${artifactId}-${version}</tag> > </configuration> > </plugin> > However the tag comes out incorrectly. > [INFO] Full run would be tagging C:\PerforceViews\... with label: > 'XXX-myproject-0.5.4-SNAPSHOT > What is the default? <tag>${artifactId}-${version}</tag> > Note: this seems to be missing from the plugin documentation, it only > mentions releaseLabel, which defaults to tag. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
