|
||||||||
|
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-232) Add verbose sett... Bob Fields (JIRA)
- [mojo-dev] [jira] (MVERSIONS-232) Add verbose... Stephen Connolly (JIRA)
- [mojo-dev] [jira] (MVERSIONS-232) Add verbose... Stephen Connolly (JIRA)
- [mojo-dev] [jira] (MVERSIONS-232) Add verbose... Bob Fields (JIRA)
- [mojo-dev] [jira] (MVERSIONS-232) Add verbose... Bob Fields (JIRA)

Hmmm, the org.codehaus.mojo.Display*UpdatesMojo classes have no unit tests today. There's only 3 test classes for the 34 classes in that package. I have a bunch of other updates I'd like to do to some of the related classes (i.e. fix compiler and javadoc warnings, add generics to Set/List/Iterator declarations, etc), I guess some new unit tests wouldn't be a bad thing.
I'll look at https://cwiki.apache.org/confluence/display/MAVENOLD/Maven+Plugin+Harness and http://maven.apache.org/plugin-developers/plugin-testing.html for suggestions on plugin testing. If nothing else, I can at least run each plugin mojo against the versions plugin itself using the invoker plugin(perhaps failing if it finds any dependencies or plugins that need updating).
I'd also like to add to the verbose functionality, to display a particular update only once for an entire maven project hierarchy. It gets a little difficult wading through all of the projects and seeing the same updates on each one.