Maven 2.x Release Plugin

SCM urls are broken for all modules, except the parent

Details

  • Type: Bug Bug
  • Status: Open Open
  • Priority: Blocker Blocker
  • Resolution: Unresolved
  • Affects Version/s: 2.0-beta-7
  • Fix Version/s: None
  • Component/s: scm
  • Number of attachments :
    0

Issue Links

is related to

Bug - A problem which impairs or prevents the functions of the product. MRELEASE-305 release:prepare forgets a slash when changing the <scm> urls

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Improvement - An improvement or enhancement to an existing feature or task. MNG-4508 No way to avoid adding artifactId to site urls

  • Minor - Minor loss of function, or other problem where easy workaround is present.
  • Open - The issue is open and ready for the assignee to start work on it.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Maria Odea Ching added a comment -

Is this the same as MRELEASE-305?

Show
Maria Odea Ching added a comment - Is this the same as MRELEASE-305 ?
Hide
Permalink
Vincent Siveton added a comment -

Sounds like or at least, it is related.

Show
Vincent Siveton added a comment - Sounds like or at least, it is related.
Benjamin Bentmann made changes -
Field Original Value New Value
Link This issue is related to MRELEASE-305 [ MRELEASE-305 ]
Hide
Permalink
Jan Dockx added a comment -

This breaks other scm setups than the most simple.
Inheritance thus cannot be used for scm, although we have "a"(nother) clear svn schema. See http://code.google.com/p/ppwcode/issues/detail?id=100

Show
Jan Dockx added a comment - This breaks other scm setups than the most simple. Inheritance thus cannot be used for scm, although we have "a"(nother) clear svn schema. See http://code.google.com/p/ppwcode/issues/detail?id=100
Arnaud Heritier made changes -
Component/s scm [ 12698 ]
Hide
Permalink
Stephen Connolly added a comment -

Is this still an issue?

Show
Stephen Connolly added a comment - Is this still an issue?
Stephen Connolly made changes -
Labels scrub-review-started
Hide
Permalink
Tobias Schöneberg added a comment -

>> Is this still an issue?

Yes, it is.
I met the same problems that are described here: http://code.google.com/p/ppwcode/issues/detail?id=100
I'm using a parent-pom that defines
<connection>scm:hg:https://(my-hg-server)/$

{project.groupId}.${project.artifactId}/</connection>

I inherit this in a child pom (not a module of the parent pom!) and in my effective pom, I end up with this:
<connection>scm:hg:https://(my-hg-server)/${project.groupId}

.$

{project.artifactId}/${project.artifactId}

/</connection>

This renders inheritance of scm-settings useless for me.

Btw, I tried it with and without a trailing slash at the end of the URL.
Im using maven 3.0.3.

Show
Tobias Schöneberg added a comment - >> Is this still an issue? Yes, it is. I met the same problems that are described here: http://code.google.com/p/ppwcode/issues/detail?id=100 I'm using a parent-pom that defines <connection>scm:hg: https://(my-hg-server)/$ {project.groupId}.${project.artifactId}/</connection> I inherit this in a child pom (not a module of the parent pom!) and in my effective pom, I end up with this: <connection>scm:hg: https://(my-hg-server)/$ {project.groupId} .$ {project.artifactId}/${project.artifactId} /</connection> This renders inheritance of scm-settings useless for me. Btw, I tried it with and without a trailing slash at the end of the URL. Im using maven 3.0.3.
Hide
Permalink
Falko Modler added a comment -

It's a general maven issue: http://jira.codehaus.org/browse/MNG-3244
Don't be misled by the title of that issue ticket - it affects all URLs, including the scm ones.

Show
Falko Modler added a comment - It's a general maven issue: http://jira.codehaus.org/browse/MNG-3244 Don't be misled by the title of that issue ticket - it affects all URLs, including the scm ones.
Hide
Permalink
Hannes Kogler added a comment - - edited

is the problem fixed already?

We have the same problem here! It seems that the maven-release-plugin automatically adds the artifactId to the end of an URL during the release:prepare execution, what leads to an error when trying to execute the release:perform goal in the next step!!!

Is there no possibility to deactivate this "function" via any parameter of the release-plugin??

By the way we are using CVS, so if we just leave out the property variable for the module in the original url-definition [scm\:cvs\:pserver\:user@server\:/path/to/cvs/project] instead of [scm\:cvs\:pserver\:user@server\:/path/to/cvs/project\:$

{project.artifactId}

] we get an error that the scm url is invalid!

So the only chance is to add the variable that is replaced by property interpolation, what ends up to the described problem...

Show
Hannes Kogler added a comment - - edited is the problem fixed already? We have the same problem here! It seems that the maven-release-plugin automatically adds the artifactId to the end of an URL during the release:prepare execution, what leads to an error when trying to execute the release:perform goal in the next step!!! Is there no possibility to deactivate this "function" via any parameter of the release-plugin?? By the way we are using CVS, so if we just leave out the property variable for the module in the original url-definition [scm\:cvs\:pserver\:user@server\:/path/to/cvs/project] instead of [scm\:cvs\:pserver\:user@server\:/path/to/cvs/project\:$ {project.artifactId} ] we get an error that the scm url is invalid! So the only chance is to add the variable that is replaced by property interpolation, what ends up to the described problem...
Hannes Kogler made changes -
Link This issue is related to MNG-4508 [ MNG-4508 ]
Hide
Permalink
Hannes Kogler added a comment -

I linked the issue to another one, which seems to describe the cause for the whole bad thing

Show
Hannes Kogler added a comment - I linked the issue to another one, which seems to describe the cause for the whole bad thing
Hide
Permalink
Darryl L. Miles added a comment -

One possible workaround is to try adding a "#" to end of the text in the super POM that sets the <scm> URL elements. This causes the unwanted appended part to become a URL fragment. You maybe lucky enough that your SCM provider ignores URL fragments.

Show
Darryl L. Miles added a comment - One possible workaround is to try adding a "#" to end of the text in the super POM that sets the <scm> URL elements. This causes the unwanted appended part to become a URL fragment. You maybe lucky enough that your SCM provider ignores URL fragments.

People

  • Assignee:
    Unassigned
    Reporter:
    Vincent Siveton
Vote (8)
Watch (6)

Dates

  • Created:
    Updated: