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

attributes will cause the current model to barf out. Can't use attributes. I am not even sure that XML PIs will survive the rewriting by the Maven Release Plugin.
My point was that when we get pom model version 5.0, it needs to allow recording the version range that the dependency is desired to be within and the version to pin it to. The mistake in the 4.0.0 model is thinking that you want version range or pinned version... you actually want both