[jira] Updated: (MRELEASE-295) Internal dependencies left at old snapshot
[ http://jira.codehaus.org/browse/MRELEASE-295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arnaud Heritier updated MRELEASE-295: - Patch Submitted: [Yes] > 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 > Components: prepare >Affects Versions: 2.0-beta-6 >Reporter: Chris Searle > Attachments: mrelease_295_test_patch.txt, 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 > test > test > pom > 1.0-SNAPSHOT > and > > test-1 > test-2 > > Then - the two modules: > test/test-1/pom.xml with > > test > test > 1.0-SNAPSHOT > > test > test-1 > 1.0-SNAPSHOT > test/test-2/pom.xml with > > test > test > 1.0-SNAPSHOT > > test > test-2 > 1.0-SNAPSHOT > > > test > test-1 > 1.0-SNAPSHOT > > > 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
[jira] Updated: (MRELEASE-295) Internal dependencies left at old snapshot
[ http://jira.codehaus.org/browse/MRELEASE-295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arnaud Heritier updated MRELEASE-295: - Component/s: prepare > 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 > Components: prepare >Affects Versions: 2.0-beta-6 >Reporter: Chris Searle > Attachments: mrelease_295_test_patch.txt, 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 > test > test > pom > 1.0-SNAPSHOT > and > > test-1 > test-2 > > Then - the two modules: > test/test-1/pom.xml with > > test > test > 1.0-SNAPSHOT > > test > test-1 > 1.0-SNAPSHOT > test/test-2/pom.xml with > > test > test > 1.0-SNAPSHOT > > test > test-2 > 1.0-SNAPSHOT > > > test > test-1 > 1.0-SNAPSHOT > > > 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
[jira] Updated: (MRELEASE-295) Internal dependencies left at old snapshot
[ http://jira.codehaus.org/browse/MRELEASE-295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samuli Saarinen updated MRELEASE-295: - Attachment: mrelease_295_test_patch.txt Patch for changing the test pom files > 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: mrelease_295_test_patch.txt, 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 > test > test > pom > 1.0-SNAPSHOT > and > > test-1 > test-2 > > Then - the two modules: > test/test-1/pom.xml with > > test > test > 1.0-SNAPSHOT > > test > test-1 > 1.0-SNAPSHOT > test/test-2/pom.xml with > > test > test > 1.0-SNAPSHOT > > test > test-2 > 1.0-SNAPSHOT > > > test > test-1 > 1.0-SNAPSHOT > > > 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
[jira] Updated: (MRELEASE-295) Internal dependencies left at old snapshot
[ http://jira.codehaus.org/browse/MRELEASE-295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Trevor Spackman updated MRELEASE-295: - Attachment: release_test.zip 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 > test > test > pom > 1.0-SNAPSHOT > and > > test-1 > test-2 > > Then - the two modules: > test/test-1/pom.xml with > > test > test > 1.0-SNAPSHOT > > test > test-1 > 1.0-SNAPSHOT > test/test-2/pom.xml with > > test > test > 1.0-SNAPSHOT > > test > test-2 > 1.0-SNAPSHOT > > > test > test-1 > 1.0-SNAPSHOT > > > 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
