You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Mark Raynsford (JIRA)" <ji...@apache.org> on 2018/08/25 18:09:00 UTC

[jira] [Comment Edited] (MNG-5951) add an option to avoid path addition to inherited URLs

    [ https://issues.apache.org/jira/browse/MNG-5951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16592665#comment-16592665 ] 

Mark Raynsford edited comment on MNG-5951 at 8/25/18 6:08 PM:
--------------------------------------------------------------

Any movement on this?

I've just discovered that I've been bitten by this: I've been publishing OSGi bundles that contain incorrect URLs due to reading from `${project.distributionManagement.site.url}`. Many of my bundles have ended up with Bundle-DocURL fields that look like this:

{noformat}
Bundle-DocURL  https://www.io7m.com/software/jspatial/com.io7m.jspatial.documentation
Bundle-DocURL  https://www.io7m.com/software/jspatial/com.io7m.jspatial.examples.swing
Bundle-DocURL  https://www.io7m.com/software/jspatial/com.io7m.jspatial.tests
{noformat}

They're supposed to look like this:

{noformat}
Bundle-DocURL  https://www.io7m.com/software/jspatial
Bundle-DocURL  https://www.io7m.com/software/jspatial
Bundle-DocURL  https://www.io7m.com/software/jspatial
{noformat}

_Edit:_ The SCM URLs are wrong too. Irritating.


was (Author: io7m):
Any movement on this?

I've just discovered that I've been bitten by this: I've been publishing OSGi bundles that contain incorrect URLs due to reading from `${project.distributionManagement.site.url}`. Many of my bundles have ended up with Bundle-DocURL fields that look like this:

{noformat}
Bundle-DocURL  https://www.io7m.com/software/jspatial/com.io7m.jspatial.documentation
Bundle-DocURL  https://www.io7m.com/software/jspatial/com.io7m.jspatial.examples.swing
Bundle-DocURL  https://www.io7m.com/software/jspatial/com.io7m.jspatial.tests
{noformat}

They're supposed to look like this:

{noformat}
Bundle-DocURL  https://www.io7m.com/software/jspatial
Bundle-DocURL  https://www.io7m.com/software/jspatial
Bundle-DocURL  https://www.io7m.com/software/jspatial
{noformat}



> add an option to avoid path addition to inherited URLs
> ------------------------------------------------------
>
>                 Key: MNG-5951
>                 URL: https://issues.apache.org/jira/browse/MNG-5951
>             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
>            Priority: Major
>             Fix For: 3.6.x-candidate
>
>         Attachments: MNG-5951.zip
>
>
> 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 
> http://my.domain.de/sites/de.enterprise.calculatorsGroupId/calculator-artifactID/1.0.0-SNAPSHOT/internetAppParentPOM/calculatorParentPom/calculator-artifactID/
> 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: http://maven.apache.org/ref/current/maven-model-builder/.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)