[
http://jira.codehaus.org/browse/MRELEASE-467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=187080#action_187080
]
Stevo Slavic commented on MRELEASE-467:
---------------------------------------
Yes, I knew that, thanks anyway. Maybe example wasn't the best, but there are
cases where modules have to be built/released together. E.g. if one wants to
share soapUI tests between two or more web services projects having common
subset of WS operations. In this case a module could be created to contain
shared soapui tests project as it's "main/resources", and it could be shared by
configuring in same way soapui-maven-plugin for each of the web service project
modules, with a shared soapui tests module defined as soapui-maven-plugin
dependency.
If all project modules share the same version, then there is a workaround, by
just using ${project.version} as plugin dependency version. This doesn't work
in previous example where shared resource module (and parent it's built
together with) has one version and project using shared resources module has a
different version, so if parent module defines plugin dependency as
${project.version}, version of module (extends parent) using shared resources
will be replaced as ${project.version} which is different from shared resources
or parent module version resulting in dependency not or wrongly resolved.
> Release preparation should update version of plugin dependencies
> ----------------------------------------------------------------
>
> Key: MRELEASE-467
> URL: http://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
> Attachments: 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 contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
