[
https://jira.codehaus.org/browse/MRELEASE-467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=312666#comment-312666
]
Stefan Schilling commented on MRELEASE-467:
-------------------------------------------
I just tried version 2.3.2, problem persists.
I was able to get around it by defining the plugin dependency yet again - as a
standard dependency of scope test (defining the version to be used in a
variable shared by dependency and plugin-dependencies).
> Release preparation should update version of plugin dependencies
> ----------------------------------------------------------------
>
> Key: MRELEASE-467
> URL: https://jira.codehaus.org/browse/MRELEASE-467
> Project: Maven 2.x Release Plugin
> Issue Type: New Feature
> Components: prepare
> Affects Versions: 2.0-beta-9
> Reporter: Stevo Slavic
> Assignee: Benjamin Bentmann
> Fix For: 2.2.2
>
> Attachments: MNG-467-maven-release.patch, whizbang.zip
>
>
> Currently plugin prepare release will update project dependencies, but not
> project plugin dependencies. Please support updating version of plugin
> dependencies as part of the prepare goal.
> This would be useful if one has a multi-module project with one module
> defining plugin with dependency to other project module, e.g. like in
> suggested handling of sharing checkstyle configuration between modules of a
> project (see
> http://maven.apache.org/plugins/maven-checkstyle-plugin/examples/multi-module-config.html
> and attached eclipse project). There one build resources module contains
> checkstyle configuration to be shared, while parent module inherited by all
> other project modules (except one with the checkstyle configuration) defines
> checkstyle plugin with added dependency to build resources module. Parent
> module defines build resources module as it's module, and both are built at
> the same time, likely all of them have same version. Currently version of
> plugin dependency version doesn't get updated automatically by prepare goal.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
