You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Olivier Lamy (JIRA)" <ji...@codehaus.org> on 2006/05/09 09:16:41 UTC

[jira] Commented: (MRELEASE-103) No SCM URL was provided to perform the release from

    [ http://jira.codehaus.org/browse/MRELEASE-103?page=comments#action_65002 ] 

Olivier Lamy commented on MRELEASE-103:
---------------------------------------

I fixed it by adding : -DconnectionUrl=scm:svn:http://57.200.0.197:7770/Accommons/olamy/trunk \ in the script buildis.sh.
Strange this should be setted with developerConnection from the root pom ?
Olivier

> No SCM URL was provided to perform the release from
> ---------------------------------------------------
>
>          Key: MRELEASE-103
>          URL: http://jira.codehaus.org/browse/MRELEASE-103
>      Project: Maven 2.x Release Plugin
>         Type: Bug

>  Environment: solaris
>     Reporter: Olivier Lamy
>     Priority: Blocker
>  Attachments: olamy.tar.gz
>
>
> The stack trace says :
> DEBUG] Trace
> org.apache.maven.BuildFailureException: No SCM URL was provided to perform the release from
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor
> .java:555)
> I included a test case with multi modules project (you need to change scm url in all poms to complete the test).
> Strange because all scm parts are filled in all modules.
> To test it, I launch ./buildis.sh $svnuser $svnpwd
> Olivier

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