|
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). 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. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Fixed in r717941
.