Maven Release Plugin
  1. Maven Release Plugin
  2. MRELEASE-331

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

        Activity

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

        Is this still an issue?

        Show
        Stephen Connolly added a comment - Is this still an issue?
        Hide
        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
        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
        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...
        Hide
        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
        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
          • Votes:
            8 Vote for this issue
            Watchers:
            8 Start watching this issue

            Dates

            • Created:
              Updated: