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

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.

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.
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
Hide
Permalink
Stephen Connolly added a comment -

Is this still an issue?

Show
Stephen Connolly added a comment - Is this still an issue?
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.

People

  • Assignee:
    Unassigned
    Reporter:
    Vincent Siveton
Vote (5)
Watch (3)

Dates

  • Created:
    Updated: