Maven 2 & 3

[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

is related to

Bug - A problem which impairs or prevents the functions of the product. MNG-3244 inherited site url not properly handling parameters

  • Major - Major loss of function.
  • Reopened - This issue was once resolved, but the resolution was deemed incorrect. From here issues are either marked assigned or resolved.

Bug - A problem which impairs or prevents the functions of the product. MNG-3254 artifactId is not appended any more in distributionManagement.site.url in multi modules when it's not defined in a child

  • 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
Benjamin Bentmann added a comment -

Fixed in r717941.

Show
Benjamin Bentmann added a comment - Fixed in r717941 .
Hide
Permalink
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
Permalink
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
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: