I've got following effect with the maven versions plugin 1.2.
If we release a milestone of our software, we declare the components which are included in the milestone with [version]-[unrel]-[revision]. When the software is in the release process, we remove the additional declaration. For example: Version 1.1.0-unrel-0038381 will be transformed to 1.1.0, so in fact, 1.1.0 is newer than 1.1.0-unrel-0038381. I don't know why the plugin acts like this: org.codehaus.mojo:versions-maven-plugin:1.2:display-dependency-updates will ... The following dependencies in Dependency Management have newer versions: SnakeYAML:SnakeYAML ....................................... 1.2 -> 1.3 mnet:comp-accessoriesconfig ............. 1.1.0 -> 1.1.0-unrel-0038381 mnet:comp-accessoriesconfig-if .......... 1.1.0 -> 1.1.0-unrel-0038381 mnet:comp-accessoriesconfigview ......... 1.1.0 -> 1.2.0-unrel-0039226 mnet:comp-accessoriesconfigview-if ...... 1.0.0 -> 1.0.0-unrel-0027036 ... Do you know why?
