[ 
http://jira.codehaus.org/browse/MVERSIONS-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=239983#action_239983
 ] 

Stephen Connolly edited comment on MVERSIONS-79 at 10/18/10 8:09 AM:
---------------------------------------------------------------------

There is a patch against MVERSIONS-125 that adds support for ranges to the 
oldVersion property. If that (or similar) is applied will this issue be 
resolved for you (a.k.a. Would you be happy if I closed this as a duplicate of 
MVERSIONS-125)

      was (Author: stephenconnolly):
    There is a patch against another jira that adds support for ranges to the 
oldVersion property
  
> Add a goal that that sets next release/development version as done in 
> release:prepare
> -------------------------------------------------------------------------------------
>
>                 Key: MVERSIONS-79
>                 URL: http://jira.codehaus.org/browse/MVERSIONS-79
>             Project: Maven 2.x Versions Plugin
>          Issue Type: New Feature
>            Reporter: Stig Kleppe-Jørgensen
>
> We have some cases where we want to increase the version to the next 
> release/development without doing a full release as done with the release 
> plugin. So having a goal in the versions plugin that does this for us would 
> have been great.
> The versions:set could have been used if it had not been for us not having 
> the same versions on all of our child modules.

-- 
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



---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply via email to