[jira] Commented: (MRELEASE-3) release:prepare should not require multimodule artifacts to be in the local repository
[ http://jira.codehaus.org/browse/MRELEASE-3?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=201562#action_201562 ] Youri De Bondt commented on MRELEASE-3: --- -DpreparationGoals="clean install" doesn't work for me. I have to perform a clean install first, then release:prepare which will check if the modules are installed, and finaly perform the clean install again. > release:prepare should not require multimodule artifacts to be in the local > repository > -- > > Key: MRELEASE-3 > URL: http://jira.codehaus.org/browse/MRELEASE-3 > Project: Maven 2.x Release Plugin > Issue Type: Bug > Components: prepare >Reporter: John Casey > Fix For: Future > > > Currently, if you try to run release:prepare on a multimodule project after > removing any of that build's artifacts from the local repository, it will > fail. Investigate why release:prepare needs the multimodule artifacts > installed in the local repository before it can succeed. > To reproduce, comment the following line in it2002/test.sh: > mvn clean install > NOTE: This may have to do with the version resolution code, which is used to > resolve SNAPSHOT versions. -- 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] Commented: (MRELEASE-3) release:prepare should not require multimodule artifacts to be in the local repository
[ http://jira.codehaus.org/browse/MRELEASE-3?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=189646#action_189646 ] Job de Noo commented on MRELEASE-3: --- have te same issue that it will not resolve reactor dependencies in maven 2.2 > release:prepare should not require multimodule artifacts to be in the local > repository > -- > > Key: MRELEASE-3 > URL: http://jira.codehaus.org/browse/MRELEASE-3 > Project: Maven 2.x Release Plugin > Issue Type: Bug > Components: prepare >Reporter: John Casey > Fix For: Future > > > Currently, if you try to run release:prepare on a multimodule project after > removing any of that build's artifacts from the local repository, it will > fail. Investigate why release:prepare needs the multimodule artifacts > installed in the local repository before it can succeed. > To reproduce, comment the following line in it2002/test.sh: > mvn clean install > NOTE: This may have to do with the version resolution code, which is used to > resolve SNAPSHOT versions. -- 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] Commented: (MRELEASE-3) release:prepare should not require multimodule artifacts to be in the local repository
[ http://jira.codehaus.org/browse/MRELEASE-3?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=154565#action_154565 ] Dan Tran commented on MRELEASE-3: - setting preparationGoals="clean install" will work, but for a large project with daily release, the build time is double. > release:prepare should not require multimodule artifacts to be in the local > repository > -- > > Key: MRELEASE-3 > URL: http://jira.codehaus.org/browse/MRELEASE-3 > Project: Maven 2.x Release Plugin > Issue Type: Bug >Reporter: John Casey >Assignee: Emmanuel Venisse > Fix For: 2.0-beta-9 > > > Currently, if you try to run release:prepare on a multimodule project after > removing any of that build's artifacts from the local repository, it will > fail. Investigate why release:prepare needs the multimodule artifacts > installed in the local repository before it can succeed. > To reproduce, comment the following line in it2002/test.sh: > mvn clean install > NOTE: This may have to do with the version resolution code, which is used to > resolve SNAPSHOT versions. -- 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] Commented: (MRELEASE-3) release:prepare should not require multimodule artifacts to be in the local repository
[ http://jira.codehaus.org/browse/MRELEASE-3?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=145261#action_145261 ] Dan Tran commented on MRELEASE-3: - I made an attempt to do a test release:prepare of surefire ( ofcourse with network cutoff) and no local artifacts mvn release:prepare -P -DpreparationGoals=clean" It went fine ( fails at expected svn commit ). So the problem is little more troubling, could be due to the way I setup up my company maven project which is much bigger then surefire. > release:prepare should not require multimodule artifacts to be in the local > repository > -- > > Key: MRELEASE-3 > URL: http://jira.codehaus.org/browse/MRELEASE-3 > Project: Maven 2.x Release Plugin > Issue Type: Bug >Reporter: John Casey >Assignee: Emmanuel Venisse > Fix For: 2.0-beta-8 > > > Currently, if you try to run release:prepare on a multimodule project after > removing any of that build's artifacts from the local repository, it will > fail. Investigate why release:prepare needs the multimodule artifacts > installed in the local repository before it can succeed. > To reproduce, comment the following line in it2002/test.sh: > mvn clean install > NOTE: This may have to do with the version resolution code, which is used to > resolve SNAPSHOT versions. -- 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] Commented: (MRELEASE-3) release:prepare should not require multimodule artifacts to be in the local repository
[ http://jira.codehaus.org/browse/MRELEASE-3?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_94907 ] Sundeep Sharma commented on MRELEASE-3: --- I am facing same issue with 2.0.6. > release:prepare should not require multimodule artifacts to be in the local > repository > -- > > Key: MRELEASE-3 > URL: http://jira.codehaus.org/browse/MRELEASE-3 > Project: Maven 2.x Release Plugin > Issue Type: Bug >Reporter: John Casey >Assignee: Emmanuel Venisse > Fix For: 2.0-beta-5 > > > Currently, if you try to run release:prepare on a multimodule project after > removing any of that build's artifacts from the local repository, it will > fail. Investigate why release:prepare needs the multimodule artifacts > installed in the local repository before it can succeed. > To reproduce, comment the following line in it2002/test.sh: > mvn clean install > NOTE: This may have to do with the version resolution code, which is used to > resolve SNAPSHOT versions. -- 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] Commented: (MRELEASE-3) release:prepare should not require multimodule artifacts to be in the local repository
[ http://jira.codehaus.org/browse/MRELEASE-3?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_93593 ] Damien Lecan commented on MRELEASE-3: - Snapshot of the plugin from rev 530675 doesn't need to have artifacts in the local repository. Good job > release:prepare should not require multimodule artifacts to be in the local > repository > -- > > Key: MRELEASE-3 > URL: http://jira.codehaus.org/browse/MRELEASE-3 > Project: Maven 2.x Release Plugin > Issue Type: Bug >Reporter: John Casey > > Currently, if you try to run release:prepare on a multimodule project after > removing any of that build's artifacts from the local repository, it will > fail. Investigate why release:prepare needs the multimodule artifacts > installed in the local repository before it can succeed. > To reproduce, comment the following line in it2002/test.sh: > mvn clean install > NOTE: This may have to do with the version resolution code, which is used to > resolve SNAPSHOT versions. -- 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] Commented: (MRELEASE-3) release:prepare should not require multimodule artifacts to be in the local repository
[ http://jira.codehaus.org/browse/MRELEASE-3?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_93489 ] Emmanuel Venisse commented on MRELEASE-3: - John, I think this problem is fixed in latest code. Can you verify? > release:prepare should not require multimodule artifacts to be in the local > repository > -- > > Key: MRELEASE-3 > URL: http://jira.codehaus.org/browse/MRELEASE-3 > Project: Maven 2.x Release Plugin > Issue Type: Bug >Reporter: John Casey > > Currently, if you try to run release:prepare on a multimodule project after > removing any of that build's artifacts from the local repository, it will > fail. Investigate why release:prepare needs the multimodule artifacts > installed in the local repository before it can succeed. > To reproduce, comment the following line in it2002/test.sh: > mvn clean install > NOTE: This may have to do with the version resolution code, which is used to > resolve SNAPSHOT versions. -- 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] Commented: (MRELEASE-3) release:prepare should not require multimodule artifacts to be in the local repository
[ http://jira.codehaus.org/browse/MRELEASE-3?page=comments#action_83778 ] Baerrach bonDierne commented on MRELEASE-3: --- MRELEASE-182 (release:prepare preparationGoals should be "clean verify") may be related to this issue. I disagree with the recommendation in MRELEASE-182 as I believe that "install" needs to happen as part of release:prepare. The scenario is this: * module projects are executed with existing default goals (clean integration-test) * deployment module gets executed which has an assembly which attempts to collect all the previous module artifact's and place them into a distributable archive. The deployment module will fail since none of the artifacts are available in the local repository. According to http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html: "package" < "integration-test" < "install" and hence the deployment module will cause failures in the release process. My workaround is to manually run mvn install when the release process fails and then to restart the release. > release:prepare should not require multimodule artifacts to be in the local > repository > -- > > Key: MRELEASE-3 > URL: http://jira.codehaus.org/browse/MRELEASE-3 > Project: Maven 2.x Release Plugin > Issue Type: Bug >Reporter: John Casey > > Currently, if you try to run release:prepare on a multimodule project after > removing any of that build's artifacts from the local repository, it will > fail. Investigate why release:prepare needs the multimodule artifacts > installed in the local repository before it can succeed. > To reproduce, comment the following line in it2002/test.sh: > mvn clean install > NOTE: This may have to do with the version resolution code, which is used to > resolve SNAPSHOT versions. -- 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] Commented: (MRELEASE-3) release:prepare should not require multimodule artifacts to be in the local repository
[ http://jira.codehaus.org/browse/MRELEASE-3?page=comments#action_76399 ] Dan Tran commented on MRELEASE-3: - John, Do you have any progress on this JIRA? I have a scenario where I need to do a release:prepare without the availablity of the snapshots. Let me know what I can do to help. > release:prepare should not require multimodule artifacts to be in the local > repository > -- > > Key: MRELEASE-3 > URL: http://jira.codehaus.org/browse/MRELEASE-3 > Project: Maven 2.x Release Plugin > Issue Type: Bug >Reporter: John Casey > Fix For: 2.0 > > > Currently, if you try to run release:prepare on a multimodule project after > removing any of that build's artifacts from the local repository, it will > fail. Investigate why release:prepare needs the multimodule artifacts > installed in the local repository before it can succeed. > To reproduce, comment the following line in it2002/test.sh: > mvn clean install > NOTE: This may have to do with the version resolution code, which is used to > resolve SNAPSHOT versions. -- 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] Commented: (MRELEASE-3) release:prepare should not require multimodule artifacts to be in the local repository
[ http://jira.codehaus.org/browse/MRELEASE-3?page=comments#action_65630 ] Brett Porter commented on MRELEASE-3: - "Project references" - I assume you mean project.getArtifact() ? This can only happen when the artifact is created (or a semblance of it) - ie at compile, package, install phases where it is target/classes, target/XXX.jar or the local repository versions respectively. > release:prepare should not require multimodule artifacts to be in the local > repository > -- > > Key: MRELEASE-3 > URL: http://jira.codehaus.org/browse/MRELEASE-3 > Project: Maven 2.x Release Plugin > Type: Bug > Reporter: John Casey > Fix For: 2.0 > > > Currently, if you try to run release:prepare on a multimodule project after > removing any of that build's artifacts from the local repository, it will > fail. Investigate why release:prepare needs the multimodule artifacts > installed in the local repository before it can succeed. > To reproduce, comment the following line in it2002/test.sh: > mvn clean install > NOTE: This may have to do with the version resolution code, which is used to > resolve SNAPSHOT versions. -- 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
