Maven
  1. Maven
  2. MNG-3846

[regression] Inherited URLs are not automatically extended with the child's artifactId

    Details

    • Complexity:
      Intermediate
    • Number of attachments :
      0

      Description

      {{$

      {project.url}

      }} is not extended.

        Issue Links

          Activity

          Hide
          Benjamin Bentmann added a comment -

          Fixed in r717941.

          Show
          Benjamin Bentmann added a comment - Fixed in r717941 .
          Hide
          Jörg Schaible added a comment -

          Please review this change also in the light of discussions for XSTR-2290, XSTR-3244 and related. It is far from clear whether appending the artifactId is a proper solution in case of an URL ending with a slash nor in case of all kind of URLs (especially the SCM ones).

          Show
          Jörg Schaible added a comment - Please review this change also in the light of discussions for XSTR-2290, XSTR-3244 and related. It is far from clear whether appending the artifactId is a proper solution in case of an URL ending with a slash nor in case of all kind of URLs (especially the SCM ones).
          Hide
          Benjamin Bentmann added a comment -

          I'm +1 on making the automatic adjusting of inherited URLs configurable (by means of some new POM element, the erroneously stated but not implemented convention with the traling slash is obscure to not say highly consfusing/suprising considering that the difference between "www.foo.org/" and "www.foo.org" in every day web browsing is usually irrelevant).

          However, I am not aware of any concrete plans to change the existing behavior and indeed the code in trunk performed this URL adjustment for (almost all) affected URLs. I merely restored full backward-compat with 2.x.

          Show
          Benjamin Bentmann added a comment - I'm +1 on making the automatic adjusting of inherited URLs configurable (by means of some new POM element, the erroneously stated but not implemented convention with the traling slash is obscure to not say highly consfusing/suprising considering that the difference between "www.foo.org/" and "www.foo.org" in every day web browsing is usually irrelevant). However, I am not aware of any concrete plans to change the existing behavior and indeed the code in trunk performed this URL adjustment for (almost all) affected URLs. I merely restored full backward-compat with 2.x.

            People

            • Assignee:
              Benjamin Bentmann
              Reporter:
              Benjamin Bentmann
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: