[
https://jira.codehaus.org/browse/MRELEASE-647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MRELEASE-647.
-----------------------------------
Resolution: Incomplete
Assignee: Robert Scholte
> Error on SVN tagging in Maven release
> --------------------------------------
>
> Key: MRELEASE-647
> URL: https://jira.codehaus.org/browse/MRELEASE-647
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Environment: Wiondows Server 2008, Tomcat 7, Jenkis 1.3.9.6 + Hudson
> Maven Release Plug-in Plug-in 0.6.1, Maven 3
> Reporter: cforce
> Assignee: Robert Scholte
>
> Checking out from the scm (https://sid-repo.de/svn/e2etrace/trunk ) does work
> and "regular" svn tag from hdsuon also, only tagging via mave release plugin
> faults with following error. Tomcat is running on local user account not
> system account.
> The scm server is using a self signed certficate.
> Manual Svn (SlikSVN 1.6.12 is installed) update from cmd prompt console as
> local user in workspace does work without problems.
> {noformat}
> [INFO]
> ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 17.547s
> [INFO] Finished at: Tue Feb 08 14:49:11 CET 2011
> [INFO] Final Memory: 14M/309M
> [INFO]
> ------------------------------------------------------------------------
> mavenExecutionResult exceptions not empty
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-release-plugin:2.0:prepare (default-cli)
> on project e2etrace: Unable to tag SCM
> Provider message:
> The svn tag command failed.
> Command output:
> svn: Can't connect to host 'sid-repo.de': No connection could be made because
> the target machine actively refused it.
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:199)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:140)
> 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:314)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:151)
> at
> org.jvnet.hudson.maven3.launcher.Maven3Launcher.main(Maven3Launcher.java:79)
> 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.launchStandard(Launcher.java:329)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:239)
> at org.jvnet.hudson.maven3.agent.Maven3Main.launch(Maven3Main.java:145)
> at hudson.maven.Maven3Builder.call(Maven3Builder.java:124)
> at hudson.maven.Maven3Builder.call(Maven3Builder.java:71)
> at hudson.remoting.UserRequest.perform(UserRequest.java:114)
> at hudson.remoting.UserRequest.perform(UserRequest.java:48)
> at hudson.remoting.Request$2.run(Request.java:270)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:619)
> Caused by: org.apache.maven.plugin.MojoFailureException: Unable to tag SCM
> Provider message:
> The svn tag command failed.
> Command output:
> svn: Can't connect to host 'sid-repo.de': No connection could be made because
> the target machine actively refused it.
> at
> org.apache.maven.plugins.release.PrepareReleaseMojo.prepareRelease(PrepareReleaseMojo.java:219)
> at
> org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareReleaseMojo.java:181)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:107)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:195)
> ... 27 more
> Caused by: org.apache.maven.shared.release.scm.ReleaseScmCommandException:
> Unable to tag SCM
> Provider message:
> The svn tag command failed.
> Command output:
> svn: Can't connect to host 'sid-repo.de': No connection could be made because
> the target machine actively refused it.
> at
> org.apache.maven.shared.release.phase.ScmTagPhase.execute(ScmTagPhase.java:118)
> at
> org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:203)
> at
> org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:140)
> at
> org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:103)
> at
> org.apache.maven.plugins.release.PrepareReleaseMojo.prepareRelease(PrepareReleaseMojo.java:211)
> ... 30 more
> channel stopped
> [WARNINGS] Skipping publisher since build result is FAILURE
> Skipping sonar analysis due to bad build status FAILURE
> {noformat}
--
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
