maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Scholte (JIRA)" <j...@codehaus.org>
Subject [jira] (MRELEASE-138) release:prepare fails when checking in modified POMs of a multi-modules project
Date Thu, 18 Oct 2012 16:59:36 GMT

     [ https://jira.codehaus.org/browse/MRELEASE-138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Robert Scholte updated MRELEASE-138:
------------------------------------

    Description: 
Here is the project structure on the disk :

{noformat}
c:\javadev\prj\myproject\module1
c:\javadev\prj\myproject\module2
c:\javadev\prj\myproject\master
{noformat}

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 :

{noformat}
[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)
....
{noformat}

The problem is that the project structure is the only one that can be used with eclipse.



  was:
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.



    
> 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 :
> {noformat}
> c:\javadev\prj\myproject\module1
> c:\javadev\prj\myproject\module2
> c:\javadev\prj\myproject\master
> {noformat}
> 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 :
> {noformat}
> [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)
> ....
> {noformat}
> 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

        

Mime
View raw message