|
||||||||
|
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-214) support semantic... Andrei Pozolotin (JIRA)
- [mojo-dev] [jira] (MVERSIONS-214) support sem... Tuomas Kiviaho (JIRA)
- [mojo-dev] [jira] (MVERSIONS-214) support sem... Stephen Connolly (JIRA)
- [mojo-dev] [jira] (MVERSIONS-214) support sem... Stephen Connolly (JIRA)
- [mojo-dev] [jira] (MVERSIONS-214) support sem... Tuomas Kiviaho (JIRA)
- [mojo-dev] [jira] (MVERSIONS-214) support sem... Stephen Connolly (JIRA)

The versions plugin is about manipulating versions in the Project Object Model itself, not about looking at the rest of the code.
As such, I think these goals fit better with the stated aims of the jardiff-maven-plugin http://mojo.codehaus.org/jardiff-maven-plugin/
Which already does some of these things (though is limited as IIRC people have not updated it to support newer bytecode versions)
It would be a good thing for somebody to revive the jardiff plugin (perhaps even rename it in the process), but I am not going to accept these goals into the versions plugin. There are too many goals already. This request is out of scope for this plugin