[jira] [Commented] (MNG-6455) ci-friendly version in parent pom displays build warning in child project
[
https://issues.apache.org/jira/browse/MNG-6455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17170736#comment-17170736
]
Johan Backlund commented on MNG-6455:
-
Brilliant, [~khmarbaise], thank you!
Sorry for not seeing this in the documentation, but googled and got this
reopened issue high in the list, thinking it was the actual problem.
> 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
> 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
(v8.3.4#803005)
[jira] [Commented] (MNG-6455) ci-friendly version in parent pom displays build warning in child project
[
https://issues.apache.org/jira/browse/MNG-6455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17170724#comment-17170724
]
Karl Heinz Marbaise commented on MNG-6455:
--
Based on the given example you are using {{mvn install}} where [in the
documentation|https://maven.apache.org/maven-ci-friendly.html#install-deploy]
explicitly stated that if you use {{install/deploy}} you *have to* configure
the {{flatten-maven-plugin}} which is responsible to resolve the special
properties. Otherwise it will not work.
The example for {{parent-pom}} does not contain a configuration for
{{flatten-maven-plugin}} which will result in such issues.
If you have *not* configured {{flatten-maven-plugin}} you can take a look into
the installed {{parent-pom.xml}} which looks like this:
{code:xml}
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd";>
4.0.0
com.example
parent-pom
${revision}
pom
1.0.0-SNAPSHOT
...
{code}
If you have configured {{flatten-maven-plugin}} the result in the
{{parent-pom.xml}} you have installed looks like this:
{code:xml}
http://maven.apache.org/POM/4.0.0
https://maven.apache.org/xsd/maven-4.0.0.xsd";
xmlns="http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
4.0.0
com.example
parent-pom
1.0.0-SNAPSHOT
pom
1.0.0-SNAPSHOT
..
{code}
> 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
> 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
(v8.3.4#803005)
[jira] [Commented] (MNG-6455) ci-friendly version in parent pom displays build warning in child project
[
https://issues.apache.org/jira/browse/MNG-6455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17170712#comment-17170712
]
Johan Backlund commented on MNG-6455:
-
I have got the same issue here using
3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
To me, the steps to reproduce as described by [~rptmaestro] demonstrates the
issue very well. I can confirm that the issue is appearing when using a
standalone parent with . And from the symptoms described by
[~Kiemes], he is probably experiencing the very same issue.
I am willing to assist if anything else is needed.
> 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
> 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
(v8.3.4#803005)
[jira] [Commented] (MNG-6455) ci-friendly version in parent pom displays build warning in child project
[
https://issues.apache.org/jira/browse/MNG-6455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17085597#comment-17085597
]
Karl Heinz Marbaise commented on MNG-6455:
--
Please [~Kiemes] make a working example
> 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
> 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
(v8.3.4#803005)
[jira] [Commented] (MNG-6455) ci-friendly version in parent pom displays build warning in child project
[
https://issues.apache.org/jira/browse/MNG-6455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17085503#comment-17085503
]
Tom Kiemes commented on MNG-6455:
-
I have the same issue in other projects. Please reopen. I could try to analyse
that together with you [~khmarbaise].
My current mvn version is 3.6.3 (latest)
Failed to build parent project for com.example:test-reactor:pom:2.0.0
org.apache.maven.project.ProjectBuildingException: Error resolving project
artifact: Failure to find com.example:parent:pom:${revision} in
http://nexus/nexus/content/groups/build.releases/ was cached in the local
repository, resolution will not be reattempted until the update interval of
central has elapsed or updates are forced for project
com.example:parent:pom:${revision}
> 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
> 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
(v8.3.4#803005)
[jira] [Commented] (MNG-6455) ci-friendly version in parent pom displays build warning in child project
[
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
, only when the parent has to be looked up from the repository.
For this reason, I set an empty 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)
[jira] [Commented] (MNG-6455) ci-friendly version in parent pom displays build warning in child project
[
https://issues.apache.org/jira/browse/MNG-6455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16676149#comment-16676149
]
Robert Thornton commented on MNG-6455:
--
I've attached the steps to reproduce. Please verify and reopen this issue.
> 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)
[jira] [Commented] (MNG-6455) ci-friendly version in parent pom displays build warning in child project
[
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)
[jira] [Commented] (MNG-6455) ci-friendly version in parent pom displays build warning in child project
[
https://issues.apache.org/jira/browse/MNG-6455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16571225#comment-16571225
]
Karl Heinz Marbaise commented on MNG-6455:
--
Can you please make a full working example of your problem...
> 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
>
> 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)
