Maven: No SCM URL was provided to perform the release from

[Dave Alvarado]

Hi,

I'm using Maven 3.0.3. I'm trying to perform a release but am getting the error …

$ mvn -e release:perform -s sonatype.xml -Dusername=myusername
[INFO] Error stacktraces are turned on.
[INFO] Scanning for projects...
[INFO]                                                                         
[INFO] ------------------------------------------------------------------------
[INFO] Building Initech Selenium Utils 1.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO] 
[INFO] --- maven-release-plugin:2.0:perform (default-cli) @ selenium-utils ---
[ERROR] No SCM URL was provided to perform the release from
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1.968s
[INFO] Finished at: Fri Jul 08 12:22:04 CDT 2011
[INFO] Final Memory: 7M/81M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.0:perform (default-cli) on project selenium-utils: No SCM URL was provided to perform the release from -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.0:perform (default-cli) on project selenium-utils: No SCM URL was provided to perform the release from
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
	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:319)
	at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
	at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
	at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
	at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
	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.launchEnhanced(Launcher.java:290)
	at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
	at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
	at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: org.apache.maven.plugin.MojoFailureException: No SCM URL was provided to perform the release from
	at org.apache.maven.plugins.release.PerformReleaseMojo.execute(PerformReleaseMojo.java:139)
	at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
	... 19 more
Caused by: org.apache.maven.shared.release.ReleaseFailureException: No SCM URL was provided to perform the release from
	at org.apache.maven.shared.release.phase.CheckCompletedPreparePhasesPhase.execute(CheckCompletedPreparePhasesPhase.java:67)
	at org.apache.maven.shared.release.DefaultReleaseManager.perform(DefaultReleaseManager.java:343)
	at org.apache.maven.shared.release.DefaultReleaseManager.perform(DefaultReleaseManager.java:289)
	at org.apache.maven.shared.release.DefaultReleaseManager.perform(DefaultReleaseManager.java:269)
	at org.apache.maven.plugins.release.PerformReleaseMojo.execute(PerformReleaseMojo.java:131)
	... 21 more

I have included a connection and URL param as part of an scm inclusion. Below is the relevant snippet from my pom.xml …

        <distributionManagement>
                <repository>
                        <id>sonatype-nexus</id>
                        <url>http://sonatype.myco.com/nexus/content/repositories/releases/</url>
                </repository>
        </distributionManagement>
        <scm>
                <developerConnection>scm:starteam:${username}@pavo.mydomain.myco.com:9999/Folder/Folder/Technology/Folder/tools/selenium</developerConnection>
                <connection>scm:starteam:${username}@pavo.mydomain.myco.com:9999/Folder/Folder/Technology/Folder/tools/selenium</connection>
                <url>https://starteam.mydomain.myco.com/BorlandStarTeam/BorlandStarTeam.jsp</url>
        </scm>
        <issueManagement>
                <system>StarTeam</system>
                <url>https://starteam.mydomain.myco.com/BorlandStarTeam/BorlandStarTeam.jsp</url>
        </issueManagement>
        <ciManagement>
                <system>Hudson</system>
                <url>http://cm-build.myco.com:8080/hudson/</url>
        </ciManagement>
</project>

Anyone know how I can cure the above problem and successfully perform a release? - Dave

[Peter Johnson]

All the documentation I have read about release:perfom is that it works only with Subversion (I have never seen a non-Subversion example). So I suspect that it doesn't know how to deal with StarTeam.

[Tim Holloway]

Peter Johnson wrote:All the documentation I have read about release:perfom is that it works only with Subversion (I have never seen a non-Subversion example). So I suspect that it doesn't know how to deal with StarTeam.

Actually, I'm pretty sure it works with CVS as well, but SVN is significant in that URL interfacing (via DAV) is one of the primary ways people deal with SVN so it comes more naturally.

If I'm not mistaken, however, the server protocol part of the module supports plug-ins. Which means that you'd need a StarTeam plugin. I don't know if one's already available, but with a little luck, at least you can find docs on how to write one.