[ 
https://issues.apache.org/jira/browse/SCM-132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17964354#comment-17964354
 ] 

Olivier Lamy commented on SCM-132:
----------------------------------

This project has moved from Jira to GitHub Issues. This issue was migrated to 
[apache/maven-scm#332|https://github.com/apache/maven-scm/issues/332]. 

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

Reply via email to