maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Struberg (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (MRELEASE-138) release:prepare fails when checking in modified POMs of a multi-modules project
Date Fri, 24 Dec 2010 12:10:58 GMT

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

Mark Struberg commented on MRELEASE-138:
----------------------------------------

I heavily use multi module projects and do not face any problems. 
So let's start with getting info about your environment situation.

.) Do you release all your projects at once from the parent module?

.) do you have a pom (build pom) in c:\javadev\prj\myproject\ ?

.) Do you invoke 
$> mvn release:prepare
on the commandline or run the goal from inside eclipse?

.) which version of maven and the release-plugin do u use?

.) do your poms contain a correct <relativePath> in the parent section?

> 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
>          Components: scm
>    Affects Versions: 2.0-beta-4
>         Environment: WinXP + Eclipse
>            Reporter: ol
>            Assignee: Emmanuel Venisse
>            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

        

Mime
View raw message