|
||||||||||||
|
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-246) Invoke versions-... Bob Fields (JIRA)
- [mojo-dev] [jira] (MVERSIONS-246) Invoke vers... Bob Fields (JIRA)
- [mojo-dev] [jira] (MVERSIONS-246) Invoke vers... Stephen Connolly (JIRA)
- [mojo-dev] [jira] (MVERSIONS-246) Invoke vers... Bob Fields (JIRA)
- [mojo-dev] [jira] (MVERSIONS-246) Invoke vers... Bob Fields (JIRA)
- [mojo-dev] [jira] (MVERSIONS-246) Invoke vers... Bob Fields (JIRA)

OK no problem (though it seems if you are running integration tests you should use the run-its profile). I created a new profile (run-plugin) which does the same thing, which must be explicitly enabled. It won't run automatically as part of the build but you can add -Prun-plugin to make that happen. Since I was wondering why this test fails with doxia 1.5 when the integration test suite succeeds, I noticed there was no test for dependency-updates-report. I'll add that (plus 3 other missing ones) in another JIRA. Updated invokeVersionsPlugin patch provided. Thanks.