[
https://issues.apache.org/jira/browse/SCM-132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17960133#comment-17960133
]
ASF GitHub Bot commented on SCM-132:
------------------------------------
jira-importer commented on issue #332:
URL: https://github.com/apache/maven-scm/issues/332#issuecomment-2964586165
**[Klaus
Brunner](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=klaus.brunner)**
commented
"extssh" is simply Eclipse's way of saying "ext using ssh as the external
rsh".
As far as I understand the Maven SCM code, using "ext" actually defaults to
trying an ssh connection anyway: see CvsConnection.connect() and the
ExtConnection class which uses a Java ssh library when no rsh is explicitly
set. So ext is extssh in fact, unless CVS_RSH is set to point to something else.
What's annoying is that there is apparently no way of setting the password
(an SCM url with "ext" doesn't allow adding the password, and it seems it's not
retrieved any other way).
> extssh connection method not shown
> ----------------------------------
>
> Key: SCM-132
> URL: https://issues.apache.org/jira/browse/SCM-132
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Bug
> Components: maven-scm-provider-cvs
> Environment: Windows 2000; Java 1.4 JDK, Maven 2.01 maven-scm-plugin
> 1.0-alpha-2
> Reporter: Todd Nine
> Priority: Major
>
> When attemping to perform a release from a project checked out from eclipse I
> receive the following error.
> [INFO] [release:prepare]
> [INFO] Verifying there are no local modifications ...
> [INFO]
> ----------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO]
> ----------------------------------------------------------------------------
> [INFO] An error is occurred in the status process.
> Embedded error: Error!
> [INFO]
> ----------------------------------------------------------------------------
> [INFO] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: An error is occurred
> in the status process.
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:555)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:485)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:455)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:303)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:216)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:139)
> 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:249)
> 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 status process.
> at
> org.apache.maven.plugins.release.PrepareReleaseMojo.checkForLocalModifications(PrepareReleaseMojo.java:514)
> at
> org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareReleaseMojo.java:201)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:432)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:530)
> ... 16 more
> Caused by: org.apache.maven.scm.ScmException: Error!
> at
> org.apache.maven.plugins.release.helpers.ScmHelper.checkResult(ScmHelper.java:124)
> at
> org.apache.maven.plugins.release.helpers.ScmHelper.getStatus(ScmHelper.java:175)
> at
> org.apache.maven.plugins.release.PrepareReleaseMojo.checkForLocalModifications(PrepareReleaseMojo.java:510)
> ... 19 more
> Since Eclipse is a commonly used IDE, is it possible to add the extssh
> connection parameter. Below is my scm from my pom.xml
> <scm>
>
> <connection>scm:cvs:ext:${maven.username}@sun10.ata.com:/a01/proj/CVS:webservices/ServiceProviders</connection>
>
> <developerConnection>scm:cvs:ext:${maven.username}@sun10.ata.com:/a01/proj/CVS:webservices/ServiceProviders</developerConnection>
> <tag>HEAD</tag>
>
> <url>http://empt.ata.com/cgi-bin/cvsweb.cgi/webservices/ServiceProviders/?cvsroot=ATA.com-Development</url>
> </scm>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
