Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Critical
-
Resolution: Fixed
-
Affects Version/s: 2.0.7
-
Fix Version/s: 2.0.8, 3.0-alpha-1
-
Component/s: Inheritance and Interpolation
-
Labels:None
-
Patch Submitted:Yes
-
Number of attachments :
Description
In the same way that the URL, and SCM inheritance assembly is 'childPathAdjustment' aware, so should the site distribution URL.
The childPathAdjustment value takes into account a child's relative location to its parent, such that 'children' (modules) that are declared via <module>../../foo/bar</module> end up with paths that are accurate for their location within the external namespaces (ie the SCM namespace or the URL namespace). However this is not being done for the site distribution URL which is obviously a bug as the project URL, which remember is childPathAdjustment aware, has a direct coupling to the distroManagement.site.URL.
Patch against maven-project 2.0.7 attached.
Attachments
Issue Links
| This issue is duplicated by: | ||||
| MNG-2209 | Calculation of module URLs does not match deployment |
|
|
|
| This issue relates to: | ||||
| MNG-5000 | [regression] child distributionManagment.site.url not correct in a flat directory layout when child's artifactId doesn't match its module name |
|
|
|
| MNG-3848 | [regression] Inheritance of project/site/scm URLs does not take child's relative location to parent into account |
|
|
|
| MNG-4994 | [regression] Inheritance of project/site/scm URLs does not take child's relative location to parent into account |
|
|
|
| This issue is related to: | ||||
| MNG-2006 | Module SCM URL is resolved as [...]/parent/module regardless of relativePath |
|
|
|
| MNG-2290 | Generated URLs in POMs of child modules |
|
|
|
Applied. Thanks, John.