[jira] Commented: (MRELEASE-138) release:prepare fails when checking in modified POMs of a multi-modules project

["Thomas Heinzelmann (JIRA)" <ji...@codehaus.org>]

    [ http://jira.codehaus.org/browse/MRELEASE-138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_86504 ] 

Thomas Heinzelmann commented on MRELEASE-138:
---------------------------------------------

Same issue for us...
We have a lot of parallel eclipse projects, the master referencing all the others. We try to convince management that we should use Maven, but since the Release-Plugin obviously isn't able to handle other than trivial eclipse-Projects (that is, parallel multi-module projects), we would have to manually change about 100 POMs per release.... which isnt't a good argument for management :-(

And there is another point: release:prepare tells
     [INFO] Full run would be tagging D:\Work\Maven-Test\cvs-test\ebtest\eb build\build with label: 'EBTEST_V1_00_00,
which implies for me that only the *master* module would be tagged.
But what about the other parallel projects? We would need to be able to specify, what exactly should be tagged 
(not only the folders where the root POMs of the projects are (e.g. eb build\build, ebbase\build), but also the parent folder (eb build, ebbase)...




> release:prepare fails when checking in modified POMs of a multi-modules project
> -------------------------------------------------------------------------------
>
>                 Key: MRELEASE-138
>                 URL: http://jira.codehaus.org/browse/MRELEASE-138
>             Project: Maven 2.x Release Plugin
>          Issue Type: Bug
>    Affects Versions: 2.0-beta-4
>         Environment: WinXP + Eclipse
>            Reporter: ol
>            Priority: Critical
>
> Here is the project structure on the disk :
> c:\javadev\prj\myproject\module1
> c:\javadev\prj\myproject\module2
> c:\javadev\prj\myproject\master
> These 3 folders represent the 3 eclipse projects, each one containing a pom.xml.
> The master project's pom is the parent of the modules.
> When I execute the release:prepare goal, Everything works fine (it asks to me the tag name, the next dev version, ...) until I receive this error :
> [INFO] Checking in modified POMs...
> [INFO] ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO] ------------------------------------------------------------------------
> [INFO] An error is occurred in the checkin process: C:\javadev\prj\myproject\module1\pom.xml was not contained in C:\javadev\prj\myproject\master
> [INFO] ------------------------------------------------------------------------
> [DEBUG] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: An error is occurred in the checkin process: C:\javadev\prj\myproject\module1\pom.xml was not contained in C:\javadev\prj\myproject\master
> 	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:559)
> 	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:488)
> 	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:458)
> ....
> The problem is that the project structure is the only one that can be used with eclipse.

-- 
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