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

The point is that these versions don't correspond with valid updates.
I have yet to find such a version that really is the latest version.
For most (possibly all?) users, showing such versions in the display-*-updates goals means that the output is useless for those particular components.
Please at least consider an optional setting to skip these versions.