maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pascal ST LAURENT (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (MRELEASE-257) Unable to do a release with release plug-in
Date Thu, 28 Jun 2007 14:10:13 GMT

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

Pascal ST LAURENT commented on MRELEASE-257:
--------------------------------------------

After some tests, I resolved temporarily this problem for me.

If I use the same url path in main pom.xml file for <SCM> connections, I receive the
exception ArrayIndexOutOfBoundsException.

Problematic configuration : 

  <scm>
    <connection>scm:svn:svn://cmappa138dev:3690/projects/pricer/releases</connection>
    <developerConnection>scm:svn:svn://cmappa138dev:3690/projects/pricer/releases</developerConnection>
  </scm>

But, if I use a different url for developerConnection, exception disappears.  Like this :

  <scm>
    <connection>scm:svn:svn://cmappa138dev:3690/projects/pricer/releases</connection>
    <developerConnection>scm:svn:svn+ssh://cmappa138dev:3690/projects/pricer/releases</developerConnection>
  </scm>

It seems to have a bug with urls check.

> Unable to do a release with release plug-in
> -------------------------------------------
>
>                 Key: MRELEASE-257
>                 URL: http://jira.codehaus.org/browse/MRELEASE-257
>             Project: Maven 2.x Release Plugin
>          Issue Type: Bug
>    Affects Versions: 2.0-beta-4
>         Environment: Windows XP SP2, Maven 2.0.7, JDK 1.5.0_10
>            Reporter: Pascal ST LAURENT
>
> When I try to do a release, I call the following statement : mvn release:prepare.  I
received this exception, maybe caused by path too long in the project...
> [ERROR] FATAL ERROR
> [INFO] ------------------------------------------------------------------------
> [INFO] 60
> [INFO] ------------------------------------------------------------------------
> [INFO] Trace
> java.lang.ArrayIndexOutOfBoundsException: 60
>         at org.apache.maven.shared.release.phase.RewritePomsForReleasePhase.translateUrlPath(RewritePomsForReleasePhase.java:249)
>         at org.apache.maven.shared.release.phase.RewritePomsForReleasePhase.translateScm(RewritePomsForReleasePhase.java:124)
>         at org.apache.maven.shared.release.phase.RewritePomsForReleasePhase.transformScm(RewritePomsForReleasePhase.java:61)
>         at org.apache.maven.shared.release.phase.AbstractRewritePomsPhase.transformDocument(AbstractRewritePomsPhase.java:271)
>         at org.apache.maven.shared.release.phase.AbstractRewritePomsPhase.transformProject(AbstractRewritePomsPhase.java:180)
>         at org.apache.maven.shared.release.phase.AbstractRewritePomsPhase.transform(AbstractRewritePomsPhase.java:116)
>         at org.apache.maven.shared.release.phase.AbstractRewritePomsPhase.execute(AbstractRewritePomsPhase.java:99)
>         at org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:194)
>         at org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:131)
>         at org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:94)
>         at org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareReleaseMojo.java:127)
>         at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:224)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
>         at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
>         at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
>         at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
>         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:585)
>         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)

-- 
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

        

Mime
View raw message