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:06:41 UTC

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

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


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

Posted by "Olivier Lamy (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MRELEASE-103?page=comments#action_65003 ] 

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

If it's required it should be set @required in the mojo ?


> 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


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

Posted by "Emmanuel Venisse (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MRELEASE-103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Emmanuel Venisse updated MRELEASE-103:
--------------------------------------

    Component/s: scm

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

        

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

Posted by "Emmanuel Venisse (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MRELEASE-103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_96268 ] 

Emmanuel Venisse commented on MRELEASE-103:
-------------------------------------------

Olivier,
Can you reproduce it with 2.0-beta-5?

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

        

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

Posted by "Chris Holman (JIRA)" <ji...@codehaus.org>.
    [ https://jira.codehaus.org/browse/MRELEASE-103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=281122#comment-281122 ] 

Chris Holman commented on MRELEASE-103:
---------------------------------------

I had the same problem, but it turned out that it was operator error.

I was trying to run release:perform before running release:prepare.

Hope this helps.

> No SCM URL was provided to perform the release from
> ---------------------------------------------------
>
>                 Key: MRELEASE-103
>                 URL: https://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.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

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

Posted by "Gabriele Columbro (JIRA)" <ji...@codehaus.org>.
    [ 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

        

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

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MRELEASE-103?page=comments#action_65010 ] 

Brett Porter commented on MRELEASE-103:
---------------------------------------

1) is already done
2) would negate the use of 1)

What I will do:
- if it is null and not in the release properties, read it from the project configuration

> 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
>      Fix For: 2.0-beta-4
>  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


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

Posted by "Olivier Lamy (JIRA)" <ji...@codehaus.org>.
    [ 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


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

Posted by "Sergey Zakusov (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MRELEASE-103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=262521#action_262521 ] 

Sergey Zakusov commented on MRELEASE-103:
-----------------------------------------

I've had the same problem with maven-release-plugin:2.1.
SCM configured like it specified by Gabriele.

> 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

        

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

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MRELEASE-103?page=comments#action_65006 ] 

Brett Porter commented on MRELEASE-103:
---------------------------------------

it reads it from the release.properties like the previous version did, but I can add it.

> 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


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

Posted by "Olivier Lamy (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MRELEASE-103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Olivier Lamy closed MRELEASE-103.
---------------------------------

       Resolution: Fixed
    Fix Version/s: 2.0-beta-5

I can't  reproduce it with 2.0-beta-5.

> 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

        

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

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MRELEASE-103?page=all ]

Brett Porter updated MRELEASE-103:
----------------------------------

    Fix Version:     (was: 2.0-beta-4)
                 2.0

> 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
>      Fix For: 2.0
>  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


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

Posted by "Olivier Lamy (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MRELEASE-103?page=comments#action_65009 ] 

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

Ok for fix version.
But just to know what will we do :
- add it in release.properties during release:prepare
- set @required in the mojo

Note it's not really a bug but just a user convenience ;-).
The plugin works like a charm.

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
>      Fix For: 2.0-beta-4
>  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


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

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MRELEASE-103?page=all ]

Brett Porter updated MRELEASE-103:
----------------------------------

    Fix Version: 2.0-beta-4

> 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
>      Fix For: 2.0-beta-4
>  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