|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
[mojo-dev] [jira] (MVERSIONS-231) display-*-updates: Option to restrict search to same major version
- [mojo-dev] [jira] (MVERSIONS-231) display-*-update... SebbASF (JIRA)
- [mojo-dev] [jira] (MVERSIONS-231) display-*-u... Stephen Connolly (JIRA)
- [mojo-dev] [jira] (MVERSIONS-231) display-*-u... SebbASF (JIRA)
- [mojo-dev] [jira] (MVERSIONS-231) display-*-u... Stephen Connolly (JIRA)
- [mojo-dev] [jira] (MVERSIONS-231) display-*-u... SebbASF (JIRA)
- [mojo-dev] [jira] (MVERSIONS-231) display-*-u... Stephen Connolly (JIRA)

If you are looking for something along the lines of http://mojo.codehaus.org/versions-maven-plugin/use-latest-releases-mojo.html#allowIncrementalUpdates and its siblings... that is probably acceptable.
My preference would be to find a way of giving indiciations within the pom as to the version ranges that a dependency should belong to in addition to the version, e.g.
<dependency> ... <version>2.0</version> <?versions [2.0,3.0)?> </dependency>