[
http://jira.codehaus.org/browse/MRELEASE-295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=129862#action_129862
]
[EMAIL PROTECTED] edited comment on MRELEASE-295 at 4/4/08 2:50 PM:
------------------------------------------------------------------
A fully-functional standalone example of this issue.
This is the command that I used to test it against 2.0-beta-4 through beta-7:
mvn -DdryRun=true clean release:clean release:prepare --batch-mode
As mentioned above, I have two modules (one called services and one called
client) that depend on the third module -- interfaces. When released, the tag
is generated appropriately, but the dependency is not updated as you would
expect -- it remains at 1.0.0-SNAPSHOT even though everything else has been
updated to 1.0.1-SNAPSHOT. The interfaces dependency has never been installed,
and is used locally in the reactor.
mvn --version info:
Maven version: 2.0.8
Java version: 1.6.0_03
OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
was (Author: [EMAIL PROTECTED]):
A fully-functional standalone example of this issue. See my post for more
info.
> Internal dependencies left at old snapshot
> ------------------------------------------
>
> Key: MRELEASE-295
> URL: http://jira.codehaus.org/browse/MRELEASE-295
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Affects Versions: 2.0-beta-6
> Reporter: Chris Searle
> Attachments: release_test.zip
>
>
> I'm having a problem with version numbering when releasing a given reactor
> with modules within the reactor that have dependencies inside the reactor.
> I have narrowed this to the following structure
> A parent test/pom.xml (basically a pom packging grouping pom - but here is
> where the scm and repos are also defined) with
> <groupId>test</groupId>
> <artifactId>test</artifactId>
> <packaging>pom</packaging>
> <version>1.0-SNAPSHOT</version>
> and
> <modules>
> <module>test-1</module>
> <module>test-2</module>
> </modules>
> Then - the two modules:
> test/test-1/pom.xml with
> <parent>
> <groupId>test</groupId>
> <artifactId>test</artifactId>
> <version>1.0-SNAPSHOT</version>
> </parent>
> <groupId>test</groupId>
> <artifactId>test-1</artifactId>
> <version>1.0-SNAPSHOT</version>
> test/test-2/pom.xml with
> <parent>
> <groupId>test</groupId>
> <artifactId>test</artifactId>
> <version>1.0-SNAPSHOT</version>
> </parent>
> <groupId>test</groupId>
> <artifactId>test-2</artifactId>
> <version>1.0-SNAPSHOT</version>
> <dependencies>
> <dependency>
> <groupId>test</groupId>
> <artifactId>test-1</artifactId>
> <version>1.0-SNAPSHOT</version>
> </dependency>
> </dependencies>
> Then run mvn -DdryRun=true release:prepare
> test/pom.xml.tag version=1.0 - good
> test/pom.xml.next version=1.1-SNAPSHOT - good
> test-1/pom.xml.tag version=1.0, parent version=1.0 good
> test-1/pom.xml.next version=1.1-SNAPSHOT, parent version=1.1-SNAPSHOT - good
> test-2/pom.xml.tag version=1.0, parent version=1.0, dependency to test-1
> version=1.0 good
> test-2/pom.xml.next version=1.1-SNAPSHOT, parent version=1.1-SNAPSHOT - good
> BUT
> test-2/pom.xml.next dependency to test-1 version=1.0-SNAPSHOT
> This seems wrong to me - I would expect it to also get 1.1-SNAPSHOT for the
> dependency on test-1 since it has the same parent and is being run in the
> same reactor.
--
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
