[
https://jira.codehaus.org/browse/MRELEASE-138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=311781#comment-311781
]
Hannes Kogler commented on MRELEASE-138:
----------------------------------------
hi!
we face the same problem with the same error message ..
message : Failed to execute goal
org.apache.maven.plugins:maven-release-plugin:2.0:prepare (default-cli) on
project basic_module: An error is occurred in the checkin process:
C:\Jenkins\workspace\basic Module\basic\pom.xml was not contained in
C:\Jenkins\workspace\basic Module\basic_module
cause : An error is occurred in the checkin process: C:\Jenkins\workspace\basic
Module\basic\pom.xml was not contained in C:\Jenkins\workspace\basic
Module\basic_module
Stack trace :
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
org.apache.maven.plugins:maven-release-plugin:2.0:prepare (default-cli) on
project basic_module: An error is occurred in the checkin process:
C:\Jenkins\workspace\basic Module\basic\pom.xml *was not contained in*
C:\Jenkins\workspace\basic Module\basic_module
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
and so perhaps it makes sense that I answer your questions: ;-)
* YES we want to release our multi-module project by running release:perform on
the pom.xml from the (parent) root project called "basic_module"!! (which is
not the parent project itself, just a project so declare the projects who
belong together by module declaration)
* YES we have a pom.xml in the basic_module project
* we run the release:prepare statement by just one click on the GUI supported
"M2 Release Plugin" for Jenkins
* Maven release plugin: 2.0 / maven installation on machine with running
Jenkins server: 3.0.4
* THATS the point where its getting interesting I think. what in your opinion
is a "correct <relativePath>" declaration? in fact we use CVS as SCM and we
have to declare the relative module declarations in a bit specialized way:
<modules>
<module>../basic</module>
<module>../basic_helper</module>
</modules>
Moreover our <relativePath> declarations uses this syntax to come out to the
parent folder =>
<relativePath>../parentProject</relativePath>
... whereas - as you see - we use different projects for our PARENT project on
the one hand (inheritance) and our project that declares multi-project modules
(reactor) on the other hand.
Is this probably a problem for the release plugin??
> release:prepare fails when checking in modified POMs of a multi-modules
> project
> -------------------------------------------------------------------------------
>
> Key: MRELEASE-138
> URL: https://jira.codehaus.org/browse/MRELEASE-138
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: scm
> Affects Versions: 2.0-beta-4
> Environment: WinXP + Eclipse
> Reporter: ol
> Assignee: Robert Scholte
> 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, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
