maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From eyal edri <eyal.e...@gmail.com>
Subject Re: No such command 'status' when running mvn release:prepare
Date Tue, 14 Sep 2010 11:15:10 GMT
I did actually, that's how i got the trace.

here's a line i noticed:

[DEBUG] Repository created: host:ctcm, port:5050, depot:CT_Dev_2.1.0,
streamName:/CT_Dev_2.1.0_eyale/Server/WebSec/ct-AutoFp, workspaceName:null,
checkoutMethod:pop, params:{}

i see the workspaceName = null, maybe there is a problem with the scm
connection str?

e.

On Tue, Sep 14, 2010 at 1:01 PM, Prashant Bhate <
prashant.mailing.list@gmail.com> wrote:

> Try running command again with verbosity
>
> mvn -X -e  release:prepare
>
> you might see some clue.
>
> Prashant Bhate
>
> On Tue, Sep 14, 2010 at 11:52 AM, eyal edri <eyal.edri@gmail.com> wrote:
>
> > Hi,
> >
> > i configured an scm in my pom.xml file:
> >
> > <scm>
> >    <connection>scm:accurev:@ctcm
> > :5050:CT_Dev_2.1.0:/Server/WebSec/ct-AutoFp</connection>
> >
> >    <developerConnection>scm:accurev:@ctcm
> > :5050:CT_Dev:/CT_Dev_2.1.0/Server/WebSec/ct-AutoFp</developerConnection>
> >
> >    <url>http://ctcm:5050</url>
> >  </scm>
> >
> > when i run mvn scm:list it works fine, but mvn release:prepare fails:
> >
> >
> > [ERROR] BUILD ERROR
> > [INFO]
> > ------------------------------------------------------------------------
> > [INFO] An error occurred during the status check process: No such command
> > 'status'.
> >
> > [INFO]
> > ------------------------------------------------------------------------
> > [DEBUG] Trace
> > org.apache.maven.lifecycle.LifecycleExecutionException: An error occurred
> > during the status check process: No such command 'status'.
> > at
> >
> >
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:719)
> >  at
> >
> >
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:569)
> > at
> >
> >
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:539)
> >  at
> >
> >
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
> > at
> >
> >
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:284)
> >  at
> >
> >
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.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:60)
> > 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.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
> > occurred
> > during the status check process: No such command 'status'.
> >  at
> >
> >
> org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareReleaseMojo.java:165)
> > at
> >
> >
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
> >  at
> >
> >
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
> > ... 17 more
> > Caused by: org.apache.maven.shared.release.ReleaseExecutionException: An
> > error occurred during the status check process: No such command 'status'.
> > at
> >
> >
> org.apache.maven.shared.release.phase.ScmCheckModificationsPhase.execute(ScmCheckModificationsPhase.java:103)
> >  at
> >
> >
> org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:196)
> > at
> >
> >
> org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:133)
> >  at
> >
> >
> org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:96)
> > at
> >
> >
> org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareReleaseMojo.java:161)
> >  ... 19 more
> > Caused by: org.apache.maven.scm.NoSuchCommandScmException: No such
> command
> > 'status'.
> > at
> >
> >
> org.apache.maven.scm.provider.AbstractScmProvider.status(AbstractScmProvider.java:646)
> >  at
> >
> >
> org.apache.maven.scm.provider.AbstractScmProvider.status(AbstractScmProvider.java:639)
> > at
> >
> >
> org.apache.maven.shared.release.phase.ScmCheckModificationsPhase.execute(ScmCheckModificationsPhase.java:98)
> >  ... 23 more
> > [INFO]
> > ------------------------------------------------------------------------
> > [INFO] Total time: 4 seconds
> > [INFO] Finished at: Tue Sep 14 12:35:20 IST 2010
> > [INFO] Final Memory: 16M/151M
> > [INFO]
> > ------------------------------------------------------------------------
> >
> >
> > Any ideas?
> >
> > --
> > Eyal Edri
> >
>



-- 
Eyal Edri

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message