Maven 2.x Release Plugin

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0-beta-5
• Fix Version/s: 2.0
• Component/s: scm
• Labels:

  None

When I try to prepare a release for my project it refuses (after project rebuild)
with such a message :
An error is occurred in the checkin process: C:\Developpement\MavenWork\SIBLING-SUBMODULE-XX\pom.xml was not contained in C:\Developpement\MavenWork\MAIN-MODULE

indeed, my project is quite complex with some modules which are sibling to the main module...
this architecture is related to the legacy, and also to the fact that Eclipse does not appreciate project inside projects.

anyway I have carefully configured the <scm><developerConnection> in each POM...

a way to do that could be to gather the SCM URLS that are used by each POM, then remove those that are included inside others, and then apply the commit/update... for every remainding.

Since many people have the same constraint (Eclipse, legacy...) this improvement would be very valuable

note that there is a similar demand for SCM update
http://jira.codehaus.org/browse/SCM-116

[INFO] BUILD SUCCESSFUL
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1 minute 23 seconds
[INFO] Finished at: Thu Apr 26 19:16:06 CEST 2007
[INFO] Final Memory: 19M/61M
[INFO] ------------------------------------------------------------------------
[INFO] Checking in modified POMs...
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] An error is occurred in the checkin process: C:\Developpement\MavenWork\FWK DEI Module Trace Manager\pom.xml was not contai
ned in C:\Developpement\MavenWork\FWK DEI Maven All

• Assignee:

  Maria Odea Ching

  Reporter:

  Alain Coetmeur

• Created:

  26/Apr/07 1:03 PM

  Updated:

  24/May/09 12:45 AM

  Resolved:

  24/May/09 12:45 AM