maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <>
Subject [jira] [Commented] (MNG-5951) add an option to avoid path addition to inherited URLs
Date Sat, 10 Sep 2016 12:52:20 GMT


Hudson commented on MNG-5951:

SUCCESS: Integrated in Jenkins build maven-3.x #1369 (See [])
MNG-5951 MNG-6059 improved inheritance documentation (hboutemy: rev 6ae831c229300e35e4630026678b8e0c03f1fc96)
* (edit) maven-model-builder/src/site/apt/index.apt

> add an option to avoid path addition to inherited URLs
> ------------------------------------------------------
>                 Key: MNG-5951
>                 URL:
>             Project: Maven
>          Issue Type: Improvement
>          Components: Inheritance and Interpolation
>    Affects Versions: 3.0.5, 3.1.1, 3.2.5, 3.3.9
>            Reporter: Jörg Sesterhenn
>            Assignee: Hervé Boutemy
>             Fix For: 3.4.0
>         Attachments:
> What I am trying to achieve is 
> the definition of a project.url in a parent pom 
> in a way that all children inherit a url ending with 
> {code}
> ${project.groupId}/${project.artifactId}/${project.version}/ 
> {code}
> in order to be able to publish sites of all artifacts in all versions in parallel
> without having to redefine the url in every child pom.
> This is currently not working as expected in maven due to the default child urls calculation
which leads to urls that add up parent urls like 
> The part *"internetAppParentPOM/calculatorParentPom/"* is added by automatic child url
calculation (those are the artifactIds of all parent poms beneath our enterprise parent pom
where the url is defined) and *is expexted to not be there at all*. The repeated artifactID
at the end of the url is superfluous as well but tollerable.
> I expect maven-core to be changed so that I can turn on/off the automatic calculation
of child URLs as an option which is by default on (current behaviour so nothing will change
unless configured explicitly).
> See the discussion in MSITE-672. 
> As this can not be done in the maven-site-plugin there needs to be a change in Maven
itself (core), in Maven Model Builder, ie the way effective model is calculated, and more
precisely in the inheritance step:

This message was sent by Atlassian JIRA

View raw message