|
||||||||||||||
|
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-230) display-*-update... SebbASF (JIRA)
- [mojo-dev] [jira] (MVERSIONS-230) display-*-u... Stephen Connolly (JIRA)
- [mojo-dev] [jira] (MVERSIONS-230) display-*-u... Stephen Connolly (JIRA)
- [mojo-dev] [jira] (MVERSIONS-230) display-*-u... SebbASF (JIRA)
- [mojo-dev] [jira] (MVERSIONS-230) display-*-u... SebbASF (JIRA)
- [mojo-dev] [jira] (MVERSIONS-230) display-*-u... Stephen Connolly (JIRA)
- [mojo-dev] [jira] (MVERSIONS-230) display-*-u... SebbASF (JIRA)
- [mojo-dev] [jira] (MVERSIONS-230) display-*-u... Stephen Connolly (JIRA)
- [mojo-dev] [jira] (MVERSIONS-230) display-*-u... SebbASF (JIRA)

They are valid version numbers. There are downstream dependencies of these versions of these artifacts. Masking the versions would not be good for users. In all cases that you have highlighted these artifacts are in the legacy groupId:artifactId scheme from Maven 1 repository import.
If you want to ignore specific versions there is the rules.xml support: http://mojo.codehaus.org/versions-maven-plugin/version-rules.html which will allow you and the projects you are working on to declare certain versions as ignored.
I am not implementing a global ignore policy as that will cause issues for users