[ http://jira.codehaus.org/browse/SCM-552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Olivier Lamy updated SCM-552: ----------------------------- Fix Version/s: 1.x > No such command 'add' using Clearcase adaptor when performing > release:prepare-with-pom > -------------------------------------------------------------------------------------- > > Key: SCM-552 > URL: http://jira.codehaus.org/browse/SCM-552 > Project: Maven SCM > Issue Type: Bug > Components: maven-plugin > Affects Versions: 2.0 > Environment: Windows XP, running Clearcase 7, Java 1.6. > Reporter: Jason Lee > Fix For: 1.x > > > When preparing the release using release:prepare-with-pom, the process can > not be completed as it seems to try to add the generated release-pom.xml into > clearcase, but received an error 'No such command 'add' ' > From the SCM matrix, it appears that this operation is valid. And ideally, I > do not want maven to automatically check in the generated files. > Below is the generated trace: > [INFO] > ------------------------------------------------------------------------ > [ERROR] BUILD ERROR > [INFO] > ------------------------------------------------------------------------ > [INFO] Cannot add release POM to SCM: No such command 'add'. > [INFO] > ------------------------------------------------------------------------ > [INFO] Trace > org.apache.maven.lifecycle.LifecycleExecutionException: Cannot add release > POM t > o SCM: No such command 'add'. > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa > ultLifecycleExecutor.java:719) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandalone > Goal(DefaultLifecycleExecutor.java:569) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau > ltLifecycleExecutor.java:539) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan > dleFailures(DefaultLifecycleExecutor.java:387) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen > ts(DefaultLifecycleExecutor.java:284) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi > fecycleExecutor.java:180) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) > at > org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:6 > 0) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. > java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces > sorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > 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: Cannot add release > PO > M to SCM: No such command 'add'. > at > org.apache.maven.plugins.release.PrepareReleaseMojo.prepareRelease(Pr > epareReleaseMojo.java:215) > at > org.apache.maven.plugins.release.PrepareWithPomReleaseMojo.execute(Pr > epareWithPomReleaseMojo.java:48) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi > nManager.java:490) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa > ultLifecycleExecutor.java:694) > ... 17 more > Caused by: org.apache.maven.shared.release.ReleaseExecutionException: Cannot > add > release POM to SCM: No such command 'add'. > at > org.apache.maven.shared.release.phase.GenerateReleasePomsPhase.addRel > easePomsToScm(GenerateReleasePomsPhase.java:199) > at > org.apache.maven.shared.release.phase.GenerateReleasePomsPhase.genera > teReleasePoms(GenerateReleasePomsPhase.java:132) > at > org.apache.maven.shared.release.phase.GenerateReleasePomsPhase.execut > e(GenerateReleasePomsPhase.java:105) > at > org.apache.maven.shared.release.phase.GenerateReleasePomsPhase.execut > e(GenerateReleasePomsPhase.java:92) > at > org.apache.maven.shared.release.DefaultReleaseManager.prepare(Default > ReleaseManager.java:203) > at > org.apache.maven.shared.release.DefaultReleaseManager.prepare(Default > ReleaseManager.java:140) > at > org.apache.maven.shared.release.DefaultReleaseManager.prepare(Default > ReleaseManager.java:103) > at > org.apache.maven.plugins.release.PrepareReleaseMojo.prepareRelease(Pr > epareReleaseMojo.java:211) > ... 20 more > Caused by: org.apache.maven.scm.NoSuchCommandScmException: No such command > 'add' > . > at > org.apache.maven.scm.provider.AbstractScmProvider.add(AbstractScmProv > ider.java:147) > at > org.apache.maven.scm.provider.AbstractScmProvider.add(AbstractScmProv > ider.java:141) > at > org.apache.maven.scm.provider.AbstractScmProvider.add(AbstractScmProv > ider.java:124) > at > org.apache.maven.shared.release.phase.GenerateReleasePomsPhase.addRel > easePomsToScm(GenerateReleasePomsPhase.java:190) > ... 27 more > Can anyone make sense of it? -- 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