maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gabriele (JIRA)" <j...@codehaus.org>
Subject [jira] (MRELEASE-128) SCM properties being replaced during release:perform
Date Tue, 20 Mar 2012 12:00:04 GMT

    [ https://jira.codehaus.org/browse/MRELEASE-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=294609#comment-294609
] 

Gabriele commented on MRELEASE-128:
-----------------------------------

I've just tryed the 2.3-SNAPSHOT, it does work for scm URL under svn when executing prepare
goal:

    <connection>scm:svn:${project.scm.url}trunk</connection>
    <developerConnection>${project.scm.connection}</developerConnection>


but when executing perform goal:

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.3
-SNAPSHOT:perform (default-cli) on project BatchSistemaInformativo: An error is
occurred in the checkout process: Exception while executing SCM command. Error w
hile executing command. Error inside systemOut parser: String index out of range
: -1 -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal o
rg.apache.maven.plugins:maven-release-plugin:2.3-SNAPSHOT:perform (default-cli)
on project BatchSistemaInformativo: An error is occurred in the checkout process
: Exception while executing SCM command.
        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)
        at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
        at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
        at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
        at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
        at org.apache.maven.cli.MavenCli.execute(MavenCli.java:534)
        at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
        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:597)
        at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
        at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
        at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
        at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: org.apache.maven.plugin.MojoExecutionException: An error is occurred in the checkout
process: Exception while executing SCM command.
        at org.apache.maven.plugins.release.PerformReleaseMojo.execute(PerformReleaseMojo.java:153)
        at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:107)
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
        ... 19 more
Caused by: org.apache.maven.shared.release.ReleaseExecutionException: An error is occurred
in the checkout process: Exception while executing SCM command.
        at org.apache.maven.shared.release.phase.CheckoutProjectFromScm.execute(CheckoutProjectFromScm.java:133)
        at org.apache.maven.shared.release.DefaultReleaseManager.perform(DefaultReleaseManager.java:421)
        at org.apache.maven.shared.release.DefaultReleaseManager.perform(DefaultReleaseManager.java:373)
        at org.apache.maven.plugins.release.PerformReleaseMojo.execute(PerformReleaseMojo.java:149)
        ... 21 more
Caused by: org.apache.maven.scm.ScmException: Exception while executing SCM command.
        at org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:63)
        at org.apache.maven.scm.provider.svn.AbstractSvnScmProvider.executeCommand(AbstractSvnScmProvider.java:356)
        at org.apache.maven.scm.provider.svn.AbstractSvnScmProvider.checkout(AbstractSvnScmProvider.java:292)
        at org.apache.maven.scm.provider.AbstractScmProvider.checkOut(AbstractScmProvider.java:480)
        at org.apache.maven.scm.provider.AbstractScmProvider.checkOut(AbstractScmProvider.java:453)
        at org.apache.maven.shared.release.phase.CheckoutProjectFromScm.performCheckout(CheckoutProjectFromScm.java:208)
        at org.apache.maven.shared.release.phase.CheckoutProjectFromScm.execute(CheckoutProjectFromScm.java:125)
        ... 24 more
Caused by: org.apache.maven.scm.ScmException: Error while executing command.
        at org.apache.maven.scm.provider.svn.svnexe.command.checkout.SvnCheckOutCommand.executeCheckOutCommand(SvnCheckOutCommand.java:95)
        at org.apache.maven.scm.command.checkout.AbstractCheckOutCommand.executeCommand(AbstractCheckOutCommand.java:82)
        at org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:59)
        ... 30 more
Caused by: org.codehaus.plexus.util.cli.CommandLineException: Error inside systemOut parser
        at org.codehaus.plexus.util.cli.CommandLineUtils$1.call(CommandLineUtils.java:194)
        at org.codehaus.plexus.util.cli.CommandLineUtils.executeCommandLine(CommandLineUtils.java:113)
        at org.codehaus.plexus.util.cli.CommandLineUtils.executeCommandLine(CommandLineUtils.java:79)
        at org.apache.maven.scm.provider.svn.svnexe.command.SvnCommandLineUtils.execute(SvnCommandLineUtils.java:146)
        at org.apache.maven.scm.provider.svn.svnexe.command.checkout.SvnCheckOutCommand.executeCheckOutCommand(SvnCheckOutCommand.java:91)
        ... 32 more
Caused by: java.lang.StringIndexOutOfBoundsException: String index out of range: -1
        at java.lang.String.substring(String.java:1937)
        at java.lang.String.substring(String.java:1904)
        at org.apache.maven.scm.provider.svn.svnexe.command.checkout.SvnCheckOutConsumer.parseLine(SvnCheckOutConsumer.java:57)
        at org.apache.maven.scm.provider.svn.svnexe.command.AbstractFileCheckingConsumer.consumeLine(AbstractFileCheckingConsumer.java:68)
        at org.codehaus.plexus.util.cli.StreamPumper.consumeLine(StreamPumper.java:190)
        at org.codehaus.plexus.util.cli.StreamPumper.run(StreamPumper.java:135)
[ERROR]
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following
articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
                
> SCM properties being replaced during release:perform
> ----------------------------------------------------
>
>                 Key: MRELEASE-128
>                 URL: https://jira.codehaus.org/browse/MRELEASE-128
>             Project: Maven 2.x Release Plugin
>          Issue Type: Bug
>          Components: prepare
>         Environment: Windows XP client, Linux repo, CVS, Maven 2.0.4
>            Reporter: Craig Dickson
>            Assignee: Robert Scholte
>            Priority: Critical
>              Labels: properties
>             Fix For: 2.3
>
>         Attachments: after-release-perform-pom.xml, after-release-prepre-pom.xml, MNG-128-maven-release-manager.patch,
MRELEASE-128_cvs_hack_RewritePomsForDevelopmentPhase.java.patch, original-pom.xml
>
>
> The <scm> section of a pom in CVS for a pom archetype project looks like this prior
to executing release:prepare :
> <scm>
> 	<connection>${base.cvs.url}:commons-maven/uber-pom</connection>
> 	<developerConnection>${base.cvs.url}:commons-maven/uber-pom</developerConnection>
> 	<url>${base.viewcvs.url}/commons-maven/uber-pom</url>
> </scm>
> Then after executing release:prepare, the pom in CVS looks like this (new <tag>
tag is only difference):
> <scm>
> 	<connection>${base.cvs.url}:commons-maven/uber-pom</connection>
> 	<developerConnection>${base.cvs.url}:commons-maven/uber-pom</developerConnection>
> 	<url>${base.viewcvs.url}/commons-maven/uber-pom</url>
> 	<tag>R-1_7</tag>
> </scm>
> Then after executing release:perform, the pom looks like this in CVS:
> <scm>
> 	<connection>scm:cvs:pserver:behrcvs.masco-coatings.com:/usr/cvsroot:commons-maven/uber-pom</connection>
> 	<developerConnection>scm:cvs:pserver:behrcvs.masco-coatings.com:/usr/cvsroot:commons-maven/uber-pom</developerConnection>
> 	<url>http://behrcvs.masco-coatings.com/cgi-bin/viewcvs.cgi/commons-maven/uber-pom</url>
> </scm>
> Notice that the properties that were there for the base URLs for CVS and ViewCVS have
been replaced with literal values. 
> No other properties in the POM are being replaced

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message