You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Dennis Lundberg (JIRA)" <ji...@codehaus.org> on 2011/01/16 21:34:58 UTC
[jira] Closed: (MCHANGES-207) Jira-Report: Allow specification of a
version-prefix
[ http://jira.codehaus.org/browse/MCHANGES-207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dennis Lundberg closed MCHANGES-207.
------------------------------------
Resolution: Fixed
Fix Version/s: 2.4
Assignee: Dennis Lundberg
Fixed in [r1059651|http://svn.apache.org/viewvc?view=revision&revision=1059651].
New 2.4-SNAPSHOT deployed. Please test it.
The new parameter is called "versionPrefix".
> Jira-Report: Allow specification of a version-prefix
> ----------------------------------------------------
>
> Key: MCHANGES-207
> URL: http://jira.codehaus.org/browse/MCHANGES-207
> Project: Maven 2.x Changes Plugin
> Issue Type: Improvement
> Components: jira
> Reporter: Michael Wenig
> Assignee: Dennis Lundberg
> Fix For: 2.4
>
>
> Currently it is possible to auto-suggest the version in jira. Therefore the version of the pom is used with '-SNAPSHOT' stripped.
> If you have a product in jira with several components it is a often used pattern to prefix the version (e.g. component1-2.0, component2-1.0 etc.)
> Currently these versions are not auto-recognized.
> It would be better if it would be possible to optionally define a prefix (in this case 'component1-').
> This would allow to use this feature also in prefixed-version-numbers
--
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