[
http://jira.codehaus.org/browse/MRELEASE-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=191372#action_191372
]
John Davis commented on MRELEASE-323:
-------------------------------------
We have found the same issue with the projects comprising our products: version
2.0-beta-9 of the Release Plugin does not update all of a project's
dependencies when used in an interactive mode.
It did not matter whether the dependencies were part of a
<dependencyManagement> section or a <dependencies> section in the POM.
For example, here is the <dependencies> section from one of our POMs.
<dependencies>
<dependency>
<groupId>openmap</groupId>
<artifactId>openmap</artifactId>
<version>4.6.5</version>
</dependency>
<dependency>
<groupId>com.echostorm.commons</groupId>
<artifactId>commons-security-api</artifactId>
<version>1.1.5-SNAPSHOT</version>
</dependency>
<dependency>
<groupId>com.echostorm.commons</groupId>
<artifactId>commons-xbroadcaster</artifactId>
<version>1.7.5-SNAPSHOT</version>
<exclusions>
<exclusion>
<groupId>log4j</groupId>
<artifactId>log4j</artifactId>
</exclusion>
</exclusions>
</dependency>
<dependency>
<groupId>com.echostorm.adlib</groupId>
<artifactId>adlib-chat-service-api</artifactId>
<version>1.0.5-SNAPSHOT</version>
</dependency>
</dependencies>
After excuting "mvn release:prepare -Dtag="adlib-3.6-rc5" -DaddSchema=false
-DpreparationGoals="clean install" ", the tagged version of the POM was:
<dependencies>
<dependency>
<groupId>openmap</groupId>
<artifactId>openmap</artifactId>
<version>4.6.5</version>
</dependency>
<dependency>
<groupId>com.echostorm.commons</groupId>
<artifactId>commons-security-api</artifactId>
<version>1.1.5-SNAPSHOT</version>
</dependency>
<dependency>
<groupId>com.echostorm.commons</groupId>
<artifactId>commons-xbroadcaster</artifactId>
<version>1.7.5-SNAPSHOT</version>
<exclusions>
<exclusion>
<groupId>log4j</groupId>
<artifactId>log4j</artifactId>
</exclusion>
</exclusions>
</dependency>
<dependency>
<groupId>com.echostorm.adlib</groupId>
<artifactId>adlib-chat-service-api</artifactId>
<version>1.0.5</version>
</dependency>
and the next development version was:
<dependencies>
<dependency>
<groupId>openmap</groupId>
<artifactId>openmap</artifactId>
<version>4.6.5</version>
</dependency>
<dependency>
<groupId>com.echostorm.commons</groupId>
<artifactId>commons-security-api</artifactId>
<version>1.1.5-SNAPSHOT</version>
</dependency>
<dependency>
<groupId>com.echostorm.commons</groupId>
<artifactId>commons-xbroadcaster</artifactId>
<version>1.7.5-SNAPSHOT</version>
<exclusions>
<exclusion>
<groupId>log4j</groupId>
<artifactId>log4j</artifactId>
</exclusion>
</exclusions>
</dependency>
<dependency>
<groupId>com.echostorm.adlib</groupId>
<artifactId>adlib-chat-service-api</artifactId>
<version>1.0.6-SNAPSHOT</version>
</dependency>
Notice that only the last dependency (adlib-chat-service-api) was updated in
the tagged and next development versions of the POM.
I applied the patch supplied by Alessandro Zucchi to version 2.0-beta-9 and
performed:
mvn release:prepare -Dtag="adlib-3.6-rc5" -DaddSchema=false
-DpreparationGoals="clean install"
The tagged version is now:
<dependencies>
<dependency>
<groupId>openmap</groupId>
<artifactId>openmap</artifactId>
<version>4.6.5</version>
</dependency>
<dependency>
<groupId>com.echostorm.commons</groupId>
<artifactId>commons-security-api</artifactId>
<version>1.1.5</version>
</dependency>
<dependency>
<groupId>com.echostorm.commons</groupId>
<artifactId>commons-xbroadcaster</artifactId>
<version>1.7.5</version>
<exclusions>
<exclusion>
<groupId>log4j</groupId>
<artifactId>log4j</artifactId>
</exclusion>
</exclusions>
</dependency>
<dependency>
<groupId>com.echostorm.adlib</groupId>
<artifactId>adlib-chat-service-api</artifactId>
<version>1.0.5</version>
</dependency>
</dependencies>
and the next development version:
<dependencies>
<dependency>
<groupId>openmap</groupId>
<artifactId>openmap</artifactId>
<version>4.6.5</version>
</dependency>
<dependency>
<groupId>com.echostorm.commons</groupId>
<artifactId>commons-security-api</artifactId>
<version>1.1.6-SNAPSHOT</version>
</dependency>
<dependency>
<groupId>com.echostorm.commons</groupId>
<artifactId>commons-xbroadcaster</artifactId>
<version>1.7.6-SNAPSHOT</version>
<exclusions>
<exclusion>
<groupId>log4j</groupId>
<artifactId>log4j</artifactId>
</exclusion>
</exclusions>
</dependency>
<dependency>
<groupId>com.echostorm.adlib</groupId>
<artifactId>adlib-chat-service-api</artifactId>
<version>1.0.6-SNAPSHOT</version>
</dependency>
</dependencies>
After applying the patch, all dependencies are updated. This was also the cases
with several other projects.
Hopefully version 2.0-beta-10 will contain this or another similar patch
resolving the issue.
Please let me know if I can be of further assistance.
Thanks,
John Davis
EchoStorm Worldwide, LLC
> Release plugin (prepare goal) doesn't update more than one snapshot
> dependencies
> --------------------------------------------------------------------------------
>
> Key: MRELEASE-323
> URL: http://jira.codehaus.org/browse/MRELEASE-323
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
> Affects Versions: 2.0-beta-7
> Environment: Any
> Reporter: Alessandro Zucchi
> Priority: Blocker
> Attachments: patch.txt, test.zip
>
>
> I have a project so structured:
> au -------- au-business
> |
> |---- au-sistema
> Dependencies in au are:
> ...
> <dependencyManagement>
> <dependencies>
> <dependency>
> <groupId>com.zucchetti.qweb.au</groupId>
> <artifactId>au-business</artifactId>
> <version>${project.version}</version>
> </dependency>
>
> <!-- external dependencies-->
> <dependency>
> <groupId>com.zucchetti.qweb.framework</groupId>
> <artifactId>sistema</artifactId>
> <version>03.00.02-SNAPSHOT</version>
> </dependency>
> <dependency>
> <groupId>com.zucchetti.qweb.framework</groupId>
> <artifactId>business</artifactId>
> <version>03.00.02-SNAPSHOT</version>
> </dependency>
> </dependencies>
> </dependencyManagement>
> ...
> Dependencies in au-business are:
> ...
> <dependencies>
> <dependency>
> <groupId>com.zucchetti.qweb.framework</groupId>
> <artifactId>business</artifactId>
> </dependency>
> </dependencies>
> ...
> Dependencies in au-sistema are:
> ...
> <dependencies>
> <dependency>
> <groupId>com.zucchetti.qweb.au</groupId>
> <artifactId>au-business</artifactId>
> </dependency>
> <dependency>
> <groupId>com.zucchetti.qweb.framework</groupId>
> <artifactId>sistema</artifactId>
> </dependency>
> </dependencies>
> ...
> When I make a mvn release:clean release:prepare of au project the plugin,
> correctly, ask me to resolve SNAPSHOTs dependencies. (framework-business &&
> framework-sistema)
> Unfortunatly at the end of the process only framework-sistema dependency (in
> au project) has been modified, while framework-business no.
> I've debuged the problem and I found that if I force the two dependencies
> (framework-sistema, framework-business) in the parent pom (pom of "au") all
> run fine (also if the process to resolve SNAPSHOT dependencies get prompted
> tree times ... too much I say ...).But I can't do this change in production.
> So, I tryed to resolve the problem.
> I've attached a patch.
> Best regards
> Alex
--
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
