You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Peter De Velder (JIRA)" <ji...@codehaus.org> on 2007/01/31 14:46:44 UTC

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

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

Peter De Velder commented on MRELEASE-138:
------------------------------------------

Same issue here : 


[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] An error is occurred in the checkin process: /home/cpdv/wrk/FOCUS_CONTAINER/focus_logging/pom.xml was not contained in /home/cpdv/wrk/FOCUS_CONTAINER/admin_focus

[INFO] ------------------------------------------------------------------------
[DEBUG] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: An error is occurred in the checkin process: /home/cpdv/wrk/FOCUS_CONTAINER/focus_logging/pom.xml was not contained in /home/cpdv/wrk/FOCUS_CONTAINER/admin_focus
        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)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:219)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:324)
        at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
        at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
        at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
        at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.MojoExecutionException: An error is occurred in the checkin process: /home/cpdv/wrk/FOCUS_CONTAINER/focus_logging/pom.xml was not contained in /home/cpdv/wrk/FOCUS_CONTAINER/admin_focus
        at org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareReleaseMojo.java:110)
        at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)
        ... 16 more
Caused by: org.apache.maven.plugins.release.ReleaseExecutionException: An error is occurred in the checkin process: /home/cpdv/wrk/FOCUS_CONTAINER/focus_logging/pom.xml was not contained in /home/cpdv/wrk/FOCUS_CONTAINER/admin_focus
        at org.apache.maven.plugins.release.phase.ScmCommitPhase.execute(ScmCommitPhase.java:94)
        at org.apache.maven.plugins.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:139)
        at org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareReleaseMojo.java:106)
        ... 18 more
Caused by: org.apache.maven.scm.ScmException: /home/cpdv/wrk/FOCUS_CONTAINER/focus_logging/pom.xml was not contained in /home/cpdv/wrk/FOCUS_CONTAINER/admin_focus
        at org.apache.maven.scm.provider.cvslib.AbstractCvsScmProvider.getRelativePath(AbstractCvsScmProvider.java:590)
        at org.apache.maven.scm.provider.cvslib.AbstractCvsScmProvider.fixUpScmFileSetAbsoluteFilePath(AbstractCvsScmProvider.java:569)
        at org.apache.maven.scm.provider.cvslib.AbstractCvsScmProvider.executeCommand(AbstractCvsScmProvider.java:430)
        at org.apache.maven.scm.provider.cvslib.AbstractCvsScmProvider.login(AbstractCvsScmProvider.java:508)
        at org.apache.maven.scm.provider.AbstractScmProvider.login(AbstractScmProvider.java:256)
        at org.apache.maven.scm.provider.AbstractScmProvider.checkIn(AbstractScmProvider.java:192)
        at org.apache.maven.plugins.release.phase.ScmCommitPhase.execute(ScmCommitPhase.java:90)
        ... 20 more
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 6 seconds
[INFO] Finished at: Wed Jan 31 13:32:49 GMT 2007
[INFO] Final Memory: 5M/11M
[INFO] ------------------------------------------------------------------------


> 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