maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Thornton (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MNG-6455) ci-friendly version in parent pom displays build warning in child project
Date Tue, 06 Nov 2018 05:14:00 GMT

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

Robert Thornton commented on MNG-6455:
--------------------------------------

[^mng-6455.zip]

^Steps to reproduce:^
 # Unzip the attached file
 # Run {{*mvn -f parent-pom.xml install*}}
 # Run {{*mvn -f child-pom.xml install*}}
 # The output will begin with the following:

{{[INFO] Scanning for projects...}}

{{Downloading from central: [https://repo.maven.apache.org/maven2/com/example/parent-pom/$%7Brevision%7D/parent-pom-$%7Brevision%7D.pom]}}

{{[WARNING] Failed to build parent project for com.example:child-bom:pom:1.0.0-SNAPSHOT}}

> ci-friendly version in parent pom displays build warning in child project
> -------------------------------------------------------------------------
>
>                 Key: MNG-6455
>                 URL: https://issues.apache.org/jira/browse/MNG-6455
>             Project: Maven
>          Issue Type: Bug
>            Reporter: Robert Thornton
>            Priority: Minor
>             Fix For: waiting-for-feedback
>
>         Attachments: mng-6455.zip
>
>
> I have a project that is using a parent project with ci-friendly versions, but while
Maven is scanning for projects, it is looking for "my-parent-$%7Brevision%7D.pom" instead
of "my-parent-1.0-a8e435".  The project builds, but a warning is printed which confuses some
of the teams using my parent pom.
> {{[INFO] Scanning for projects...}}
> {{Downloading from mvn-lds: https://code.myserver.org/artifactory/mvn-repo/my/stack/platform/my-parent/$%7Brevision%7D/my-parent-$%7Brevision%7D.pom}}
> {{[WARNING] Failed to build parent project for my.stack.platform:my-project:pom:4.8.2.RELEASE}}
>  
> I've tracked the issue down to DefaultProjectBuilder, line 671 where `project.getParentArtifact()`
is returning an Artifact object with the unresolved version.



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

Mime
View raw message