maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Hervé Boutemy (JIRA) <j...@apache.org>
Subject [jira] [Closed] (MNG-6599) unknown version in model id when version is defined from parent
Date Tue, 12 Mar 2019 06:40:00 GMT

     [ https://issues.apache.org/jira/browse/MNG-6599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Hervé Boutemy closed MNG-6599.
------------------------------
    Resolution: Fixed

done in https://gitbox.apache.org/repos/asf?p=maven.git&a=commit&h=37676a26170be85879273a4c5a019019733ad508

> unknown version in model id when version is defined from parent
> ---------------------------------------------------------------
>
>                 Key: MNG-6599
>                 URL: https://issues.apache.org/jira/browse/MNG-6599
>             Project: Maven
>          Issue Type: Bug
>          Components: Inheritance and Interpolation
>    Affects Versions: 3.6.0
>            Reporter: Hervé Boutemy
>            Assignee: Hervé Boutemy
>            Priority: Major
>             Fix For: 3.6.1
>
>
> working on MPH-160 limitation
> bq. parent POM version is not recognized, leading to suboptimal output "<!-- org.apache.maven.plugins:maven-plugins:[unknown-version]
/home/herve/.m2/repository/org/apache/maven/plugins/maven-plugins/33/maven-plugins-33.pom,
line 198 -->"
> if we look at this pom:
> {code:xml}<project>
>   <parent>
>     <groupId>org.apache.maven</groupId>
>     <artifactId>maven-parent</artifactId>
>     <version>33</version>
>   </parent>
>   <groupId>org.apache.maven.plugins</groupId>
>   <artifactId>maven-plugins</artifactId>
>   <packaging>pom</packaging>
> ...{code}
> the fact that version is not defined as project.version but should be extrapolated from
project.parent.version seems to cause the issue in model id calculation for input source tracking



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

Mime
View raw message