[
https://issues.apache.org/jira/browse/MNG-6455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16676157#comment-16676157
]
Robert Thornton commented on MNG-6455:
--------------------------------------
Note that this issue does not happen when the parent is discoverable via
<relativePath>, only when the parent has to be looked up from the repository.
For this reason, I set an empty <relativePath/> to force parent lookup from the
repository.
My use case is that my parent pom is reused by many projects in my
organization, each having their own source code repository. Because my pom has
to be looked up, that is why my users are seeing the "Failed to build parent
project" error every time they build, and I have to continually reassure them
that there is nothing wrong with their build.
> 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)
