|
||||||||
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-244) Update dependenc... Bob Fields (JIRA)
- [mojo-dev] [jira] (MVERSIONS-244) Update depe... Bob Fields (JIRA)
- [mojo-dev] [jira] (MVERSIONS-244) Update depe... Bob Fields (JIRA)
- [mojo-dev] [jira] (MVERSIONS-244) Update depe... Bob Fields (JIRA)
- [mojo-dev] [jira] (MVERSIONS-244) Update depe... Stephen Connolly (JIRA)
- [mojo-dev] [jira] (MVERSIONS-244) Update depe... Stephen Connolly (JIRA)
- [mojo-dev] [jira] (MVERSIONS-244) Update depe... Bob Fields (JIRA)
- [mojo-dev] [jira] (MVERSIONS-244) Update depe... Bob Fields (JIRA)
- [mojo-dev] [jira] (MVERSIONS-244) Update depe... Stephen Connolly (JIRA)
Using $
{project.version}in reporting plugins will work as long as you don't run versions:*-report from the local versions-maven-plugin directory before you perform a local build (which installs the release/snapshot version in the local repo). But if that makes the project unreleasable, no problem. Adding the invoker build step to run the versions-maven-plugin against the current versions-maven-plugin GAV will accomplish the same goal. It runs as part of the install phase, after the artifact version is installed locally.
Thanks for applying the patch so quickly, I have a few more I'd like to add (i.e. adding Collection generics, fixing compiler warnings, update to maven3 API). I hope they won't conflict with any work to be done towards v3.0-SNAPSHOT.