[
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
