Maven 2.x Release Plugin

No SCM URL was provided to perform the release from

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Blocker Blocker
  • Resolution: Fixed
  • Affects Version/s: None
  • Fix Version/s: 2.0-beta-5
  • Component/s: scm
  • Labels:
    None
  • Environment:
    solaris
  • Testcase included:
    yes
  • Number of attachments :
    1

Description

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

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Olivier Lamy added a comment -

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

Show
Olivier Lamy added a comment - 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
Hide
Permalink
Olivier Lamy added a comment -

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

Show
Olivier Lamy added a comment - If it's required it should be set @required in the mojo ?
Hide
Permalink
Brett Porter added a comment -

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

Show
Brett Porter added a comment - it reads it from the release.properties like the previous version did, but I can add it.
Hide
Permalink
Olivier Lamy added a comment -

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

Show
Olivier Lamy added a comment - 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
Hide
Permalink
Brett Porter added a comment -

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
Show
Brett Porter added a comment - 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
Hide
Permalink
Emmanuel Venisse added a comment -

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

Show
Emmanuel Venisse added a comment - Olivier, Can you reproduce it with 2.0-beta-5?
Hide
Permalink
Olivier Lamy added a comment -

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

Show
Olivier Lamy added a comment - I can't reproduce it with 2.0-beta-5.
Hide
Permalink
Gabriele Columbro added a comment -

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?

Show
Gabriele Columbro added a comment - 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?
Hide
Permalink
Sergey Zakusov added a comment -

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

Show
Sergey Zakusov added a comment - I've had the same problem with maven-release-plugin:2.1. SCM configured like it specified by Gabriele.
Hide
Permalink
Chris Holman added a comment -

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.

Show
Chris Holman added a comment - 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.

People

  • Assignee:
    Unassigned
    Reporter:
    Olivier Lamy
Vote (1)
Watch (2)

Dates

  • Created:
    Updated:
    Resolved: