[
http://jira.codehaus.org/browse/MVERSIONS-24?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Gier closed MVERSIONS-24.
------------------------------
Resolution: Fixed
Fix Version/s: 1.0-alpha-3
Fixed in
[r9493|http://fisheye.codehaus.org/changelog/mojo/trunk/mojo/versions-maven-plugin?cs=9493].
I used the combined "includes" and "excludes" syntax that was discussed on the
[mailing
list|http://www.nabble.com/Question-about-include-vs-includeGroupIds%2CincludeArtifactIds-td23082618.html]
> Enable resolution of dependency version ranges
> ----------------------------------------------
>
> Key: MVERSIONS-24
> URL: http://jira.codehaus.org/browse/MVERSIONS-24
> Project: Maven 2.x Versions Plugin
> Issue Type: New Feature
> Reporter: Paul Gier
> Assignee: Paul Gier
> Fix For: 1.0-alpha-3
>
>
> It would be helpful when deploying to be have the option to change the
> dependency version ranges to the specific version used during that build.
> This would allow the local pom to contain a version range for one or more
> dependencies, but the deployed pom in the repository (and in the tag when
> releasing) would collapse the range into the version that was used during the
> build.
--
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
