You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "ol (JIRA)" <ji...@codehaus.org> on 2006/07/06 10:06:22 UTC
[jira] Created: (MRELEASE-138) release:prepare fails when checking
in modified POMs of a multi-modules project
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
Type: Bug
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
[jira] (MRELEASE-138) release:prepare fails when checking in
modified POMs of a multi-modules project
Posted by "Hannes Kogler (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=313314#comment-313314 ]
Hannes Kogler edited comment on MRELEASE-138 at 11/10/12 5:33 AM:
------------------------------------------------------------------
thanx for attaching my patch, but how will the release-process will take place now?
moreover there are several other issues who rely on the same problem:
http://jira.codehaus.org/browse/MRELEASE-633
http://jira.codehaus.org/browse/MRELEASE-516
http://jira.codehaus.org/browse/MRELEASE-261
.. now flat directory structure should also be supported for Tagging/Branching aso. (in combination with CVS too!)! just using the commitByProject flag!
PLEASE just make a NEW RELEASE of THE PLUGIN with those changes to honor the time (and money) spent into these issues!
Who has RELEASE rights for the Maven Release Plugin???
was (Author: ntshko):
thanx for attaching my patch, but how will the release-process will take place now?
moreover there are several other issues who rely on the same problem:
http://jira.codehaus.org/browse/MRELEASE-633
http://jira.codehaus.org/browse/MRELEASE-516
http://jira.codehaus.org/browse/MRELEASE-261
.. now flat directory structure should also be supported in combination with CVS! just using the commitByProject flag!
PLEASE just make a NEW RELEASE of THE PLUGIN with those changes to honor the time (and money) spent into these issues!
Who has RELEASE rights for the Maven 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
> Attachments: MRELEASE-138.patch
>
>
> 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
[jira] (MRELEASE-138) release:prepare fails when checking in
modified POMs of a multi-modules project
Posted by "Hannes Kogler (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=311854#comment-311854 ]
Hannes Kogler edited comment on MRELEASE-138 at 10/19/12 9:31 AM:
------------------------------------------------------------------
I successfully validated my SCM URL this moment.
I think it just fails because of the "flat structure" topic...
Or have u worked with such flat structures successfully too already?
was (Author: ntshko):
I successfully validated my SCM URL this moment.
I think it just fails because of the "flat structure" topic...
Or have u worked with such flat structures too already?
> 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
[jira] (MRELEASE-138) release:prepare fails when checking in
modified POMs of a multi-modules project
Posted by "Robert Scholte (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Scholte closed MRELEASE-138.
-----------------------------------
Resolution: Incomplete
Assignee: Robert Scholte (was: Emmanuel Venisse)
No feedback from users, closing it as {{incomplete}}
> 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
[jira] (MRELEASE-138) release:prepare fails when checking in
modified POMs of a multi-modules project
Posted by "Hannes Kogler (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] (MRELEASE-138) release:prepare fails when checking in
modified POMs of a multi-modules project
Posted by "Robert Scholte (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=311798#comment-311798 ]
Robert Scholte commented on MRELEASE-138:
-----------------------------------------
Please, first lock the version of the maven-release-plugin to the most recent release (currently 2.3.2) to check if this is still an issue.
> 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
[jira] (MRELEASE-138) release:prepare fails when checking in
modified POMs of a multi-modules project
Posted by "Robert Scholte (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Scholte reopened MRELEASE-138:
-------------------------------------
> 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
[jira] (MRELEASE-138) release:prepare fails when checking in
modified POMs of a multi-modules project
Posted by "Robert Scholte (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=296988#comment-296988 ]
Robert Scholte commented on MRELEASE-138:
-----------------------------------------
If nobody can answer Marks questions I'd have to close this as incomplete. There are enough multi-module projects who can release without a problem.
> 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: 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, 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
[jira] (MRELEASE-138) release:prepare fails when checking in
modified POMs of a multi-modules project
Posted by "Robert Scholte (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Scholte updated MRELEASE-138:
------------------------------------
Attachment: MRELEASE-138.patch
Patch contributed by Hannes Kogler
> 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
> Attachments: MRELEASE-138.patch
>
>
> 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
[jira] (MRELEASE-138) release:prepare fails when checking in
modified POMs of a multi-modules project
Posted by "Hannes Kogler (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=311831#comment-311831 ]
Hannes Kogler commented on MRELEASE-138:
----------------------------------------
thx for the fast answer!
I tried it again with the newest version of the release plugin. And I also adapted my execution goals to be sure, that the error doesn't "just" come across the release:perform process.
so now I really only try the following execution:
*Executing Maven: -B -f C:\Jenkins\workspace\basic Module\basic_module\pom.xml -DdevelopmentVersion=0.0.2-SNAPSHOT -DreleaseVersion=0.0.1 -Dresume=false -Dmaven.scm.provider.cvs.implementation=cvs_native release:prepare -DcommitByProject=true*
now I get following error:
mavenExecutionResult exceptions not empty
message : Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.3.2:prepare (default-cli) on project basic_module: The scm url is invalid.
- Unknown transport: pserver
cause : The scm url is invalid.
- Unknown transport: pserver
Stack trace :
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.3.2:prepare (default-cli) on project basic_module: The scm url is invalid.
- Unknown transport: pserver
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
I've already read an other reporting of this error anywhere on the net.. so obviously this problem isn't fixed at all, even on the prepare goal :-/
> 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
[jira] Updated: (MRELEASE-138) release:prepare fails when checking
in modified POMs of a multi-modules project
Posted by "Emmanuel Venisse (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Venisse updated MRELEASE-138:
--------------------------------------
Component/s: scm
> 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
> 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
[jira] (MRELEASE-138) release:prepare fails when checking in
modified POMs of a multi-modules project
Posted by "Hannes Kogler (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=313314#comment-313314 ]
Hannes Kogler edited comment on MRELEASE-138 at 11/10/12 4:48 AM:
------------------------------------------------------------------
thanx for attaching my patch, but how will the release-process will take place now?
moreover there are several other issues who rely on the same problem:
http://jira.codehaus.org/browse/MRELEASE-633
http://jira.codehaus.org/browse/MRELEASE-516
http://jira.codehaus.org/browse/MRELEASE-261
.. now flat directory structure should also be supported in combination with CVS! just using the commitByProject flag!
PLEASE just make a NEW RELEASE of THE PLUGIN with those changes to honor the time (and money) spent into these issues!
Who has RELEASE rights for the Maven Release Plugin???
was (Author: ntshko):
thanx for attaching my patch, but how will the release-process will take place now?
moreover there are several other issues who rely on the same problem:
http://jira.codehaus.org/browse/MRELEASE-633
http://jira.codehaus.org/browse/MRELEASE-516
http://jira.codehaus.org/browse/MRELEASE-261
.. now flat directory structure should also be supported in combination of CVS! just using the commitByProject flag!
PLEASE just make a NEW RELEASE of THE PLUGIN with those changes to honor the time (and money) spent into these issues!
Who has RELEASE rights for the Maven 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
> Attachments: MRELEASE-138.patch
>
>
> 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
[jira] Commented: (MRELEASE-138) release:prepare fails when
checking in modified POMs of a multi-modules project
Posted by "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
[jira] Commented: (MRELEASE-138) release:prepare fails when
checking in modified POMs of a multi-modules project
Posted by "Peter De Velder (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] (MRELEASE-138) release:prepare fails when checking in
modified POMs of a multi-modules project
Posted by "Hannes Kogler (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=311831#comment-311831 ]
Hannes Kogler edited comment on MRELEASE-138 at 10/19/12 3:26 AM:
------------------------------------------------------------------
thx for the fast answer!
I tried it again with the newest version of the release plugin. And I also adapted my execution goals to be sure, that the error doesn't "just" come across the release:perform process.
so now I really only try the following execution:
*Executing Maven: -B -f C:\Jenkins\workspace\basic Module\basic_module\pom.xml -DdevelopmentVersion=0.0.2-SNAPSHOT -DreleaseVersion=0.0.1 -Dresume=false -Dmaven.scm.provider.cvs.implementation=cvs_native release:prepare -DcommitByProject=true*
now I get following error:
mavenExecutionResult exceptions not empty
message : Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.3.2:prepare (default-cli) on project basic_module: The scm url is invalid.
- Unknown transport: pserver
cause : The scm url is invalid.
- Unknown transport: pserver
Stack trace :
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.3.2:prepare (default-cli) on project basic_module: The scm url is invalid.
- Unknown transport: pserver
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
I've already read an other reporting of this error anywhere on the net.. so obviously this problem isn't fixed at all, even on the prepare goal :-/
It's kind of funny, because he writes that the SCM URL is invalid BUT on the other hand the checkin of the changed versioninfo in the pom from 0.0.1-SNAPSHOT to 0.0.1 is commited indeed.
was (Author: ntshko):
thx for the fast answer!
I tried it again with the newest version of the release plugin. And I also adapted my execution goals to be sure, that the error doesn't "just" come across the release:perform process.
so now I really only try the following execution:
*Executing Maven: -B -f C:\Jenkins\workspace\basic Module\basic_module\pom.xml -DdevelopmentVersion=0.0.2-SNAPSHOT -DreleaseVersion=0.0.1 -Dresume=false -Dmaven.scm.provider.cvs.implementation=cvs_native release:prepare -DcommitByProject=true*
now I get following error:
mavenExecutionResult exceptions not empty
message : Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.3.2:prepare (default-cli) on project basic_module: The scm url is invalid.
- Unknown transport: pserver
cause : The scm url is invalid.
- Unknown transport: pserver
Stack trace :
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.3.2:prepare (default-cli) on project basic_module: The scm url is invalid.
- Unknown transport: pserver
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
I've already read an other reporting of this error anywhere on the net.. so obviously this problem isn't fixed at all, even on the prepare goal :-/
> 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
[jira] (MRELEASE-138) release:prepare fails when checking in
modified POMs of a multi-modules project
Posted by "Hannes Kogler (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=313314#comment-313314 ]
Hannes Kogler commented on MRELEASE-138:
----------------------------------------
thanx for attaching my patch, but how will the release-process will take place now?
moreover there are several other issues who rely on the same problem:
http://jira.codehaus.org/browse/MRELEASE-633
http://jira.codehaus.org/browse/MRELEASE-516
http://jira.codehaus.org/browse/MRELEASE-261
.. now flat directory structure should also be supported in combination of CVS! just using the commitByProject flag!
PLEASE just make a NEW RELEASE of THE PLUGIN with those changes to honor the time (and money) spent into this issues!
Who has RELEASE rights for the Maven 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
> Attachments: MRELEASE-138.patch
>
>
> 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
[jira] Commented: (MRELEASE-138) release:prepare fails when
checking in modified POMs of a multi-modules project
Posted by "Mark Struberg (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] (MRELEASE-138) release:prepare fails when checking in
modified POMs of a multi-modules project
Posted by "Robert Scholte (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Reopened: (MRELEASE-138) release:prepare fails when checking
in modified POMs of a multi-modules project
Posted by "ol (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ol reopened MRELEASE-138:
-------------------------
I think this issue is linked to MRELEASE-261.
It's not a duplicate of MRELEASE-6.
I 'm still facing errors when trying to release a parent project that have some modules in another folder :
\parent
\moduleA
\moduleB
> 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
[jira] (MRELEASE-138) release:prepare fails when checking in
modified POMs of a multi-modules project
Posted by "Hannes Kogler (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=313314#comment-313314 ]
Hannes Kogler edited comment on MRELEASE-138 at 11/10/12 4:47 AM:
------------------------------------------------------------------
thanx for attaching my patch, but how will the release-process will take place now?
moreover there are several other issues who rely on the same problem:
http://jira.codehaus.org/browse/MRELEASE-633
http://jira.codehaus.org/browse/MRELEASE-516
http://jira.codehaus.org/browse/MRELEASE-261
.. now flat directory structure should also be supported in combination of CVS! just using the commitByProject flag!
PLEASE just make a NEW RELEASE of THE PLUGIN with those changes to honor the time (and money) spent into these issues!
Who has RELEASE rights for the Maven Release Plugin???
was (Author: ntshko):
thanx for attaching my patch, but how will the release-process will take place now?
moreover there are several other issues who rely on the same problem:
http://jira.codehaus.org/browse/MRELEASE-633
http://jira.codehaus.org/browse/MRELEASE-516
http://jira.codehaus.org/browse/MRELEASE-261
.. now flat directory structure should also be supported in combination of CVS! just using the commitByProject flag!
PLEASE just make a NEW RELEASE of THE PLUGIN with those changes to honor the time (and money) spent into this issues!
Who has RELEASE rights for the Maven 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
> Attachments: MRELEASE-138.patch
>
>
> 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
[jira] Closed: (MRELEASE-138) release:prepare fails when checking
in modified POMs of a multi-modules project
Posted by "Emmanuel Venisse (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Venisse closed MRELEASE-138.
-------------------------------------
Assignee: Emmanuel Venisse
Resolution: Duplicate
> 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
> Assigned To: 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
[jira] (MRELEASE-138) release:prepare fails when checking in
modified POMs of a multi-modules project
Posted by "Hannes Kogler (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=311831#comment-311831 ]
Hannes Kogler edited comment on MRELEASE-138 at 10/19/12 3:37 AM:
------------------------------------------------------------------
thx for the fast answer!
I tried it again with the newest version of the release plugin. And I also adapted my execution goals to be sure, that the error doesn't "just" come across the release:perform process.
so now I really only try the following execution:
*Executing Maven: -B -f C:\Jenkins\workspace\basic Module\basic_module\pom.xml -DdevelopmentVersion=0.0.2-SNAPSHOT -DreleaseVersion=0.0.1 -Dresume=false -Dmaven.scm.provider.cvs.implementation=cvs_native release:prepare -DcommitByProject=true*
now I get following error:
mavenExecutionResult exceptions not empty
message : Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.3.2:prepare (default-cli) on project basic_module: The scm url is invalid.
- Unknown transport: pserver
cause : The scm url is invalid.
- Unknown transport: pserver
Stack trace :
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.3.2:prepare (default-cli) on project basic_module: The scm url is invalid.
- Unknown transport: pserver
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
I've already read an other reporting of this error anywhere on the net.. so obviously this problem isn't fixed at all, even on the prepare goal :-/
It's kind of funny, because he writes that the SCM URL is invalid BUT on the other hand the checkin of the changed versioninfo in the pom from 0.0.1-SNAPSHOT to 0.0.1 is commited indeed.
_UPDATE:_
Now I tried it again without the commitByProject setted. Then I run again in the error: C:\Jenkins\workspace\basic Module\basic\pom.xml was not contained in C:\Jenkins\workspace\basic Module\basic_module
*So to prevent the "was not contained in" error the "commitByProject" parameter works fine*, but everything concerning the SCM checkin (especially the tagging, also on the prepare goal) is still failing at all!!
was (Author: ntshko):
thx for the fast answer!
I tried it again with the newest version of the release plugin. And I also adapted my execution goals to be sure, that the error doesn't "just" come across the release:perform process.
so now I really only try the following execution:
*Executing Maven: -B -f C:\Jenkins\workspace\basic Module\basic_module\pom.xml -DdevelopmentVersion=0.0.2-SNAPSHOT -DreleaseVersion=0.0.1 -Dresume=false -Dmaven.scm.provider.cvs.implementation=cvs_native release:prepare -DcommitByProject=true*
now I get following error:
mavenExecutionResult exceptions not empty
message : Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.3.2:prepare (default-cli) on project basic_module: The scm url is invalid.
- Unknown transport: pserver
cause : The scm url is invalid.
- Unknown transport: pserver
Stack trace :
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.3.2:prepare (default-cli) on project basic_module: The scm url is invalid.
- Unknown transport: pserver
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
I've already read an other reporting of this error anywhere on the net.. so obviously this problem isn't fixed at all, even on the prepare goal :-/
It's kind of funny, because he writes that the SCM URL is invalid BUT on the other hand the checkin of the changed versioninfo in the pom from 0.0.1-SNAPSHOT to 0.0.1 is commited indeed.
> 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
[jira] (MRELEASE-138) release:prepare fails when checking in
modified POMs of a multi-modules project
Posted by "Robert Scholte (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=311852#comment-311852 ]
Robert Scholte commented on MRELEASE-138:
-----------------------------------------
I've worked with cvs + maven-release-plugin recently, so I know that it will work. Not sure what you found on the net, but it looks to me you're trusting the wrong resources. Have a look at http://maven.apache.org/scm/cvs.html and make sure that the URL starts with 'scm:'.
IIRC you should be able validate that URL by just calling {{mvn scm:validate}} in the execution-folder.
> 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
[jira] (MRELEASE-138) release:prepare fails when checking in
modified POMs of a multi-modules project
Posted by "Hannes Kogler (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=311854#comment-311854 ]
Hannes Kogler commented on MRELEASE-138:
----------------------------------------
I successfully validated my SCM URL this moment.
I think it just fails because of the "flat structure" topic...
Or have u worked with such flat structures too already?
> 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
[jira] (MRELEASE-138) release:prepare fails when checking in
modified POMs of a multi-modules project
Posted by "Hannes Kogler (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=313314#comment-313314 ]
Hannes Kogler edited comment on MRELEASE-138 at 11/10/12 5:34 AM:
------------------------------------------------------------------
thanx for attaching my patch, but how will the release-process will take place now?
moreover there are several other issues who rely on the same problem:
http://jira.codehaus.org/browse/MRELEASE-633
http://jira.codehaus.org/browse/MRELEASE-516
http://jira.codehaus.org/browse/MRELEASE-261
*.. now flat directory structure should also be supported for Tagging/Branching aso. (in combination with CVS too!)! just using the commitByProject flag!*
*PLEASE just make a NEW RELEASE (2.4) of THE PLUGIN with those changes to honor the time (and money) spent into these issues!*
Who has RELEASE rights for the Maven Release Plugin???
was (Author: ntshko):
thanx for attaching my patch, but how will the release-process will take place now?
moreover there are several other issues who rely on the same problem:
http://jira.codehaus.org/browse/MRELEASE-633
http://jira.codehaus.org/browse/MRELEASE-516
http://jira.codehaus.org/browse/MRELEASE-261
.. now flat directory structure should also be supported for Tagging/Branching aso. (in combination with CVS too!)! just using the commitByProject flag!
PLEASE just make a NEW RELEASE of THE PLUGIN with those changes to honor the time (and money) spent into these issues!
Who has RELEASE rights for the Maven 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
> Attachments: MRELEASE-138.patch
>
>
> 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