You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Gabriele Columbro (JIRA)" <ji...@codehaus.org> on 2009/03/18 08:49:12 UTC
[jira] Commented: (MRELEASE-103) No SCM URL was provided to perform
the release from
[ http://jira.codehaus.org/browse/MRELEASE-103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=170083#action_170083 ]
Gabriele Columbro commented on MRELEASE-103:
--------------------------------------------
I'm having this issue with 2.0-beta-8 and pom completely configured with:
<scm>
<developerConnection>scm:svn:${svn.url}</developerConnection>
<url>${svn.url}</url>
<connection>scm:svn:${svn.url}</connection>
</scm>
and
<svn.url>http://mysvnurl.com/repos/project/trunk</svn.url>
Am I missing something?
> 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
> Issue Type: Bug
> Components: scm
> Environment: solaris
> Reporter: Olivier Lamy
> Priority: Blocker
> Fix For: 2.0-beta-5
>
> 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