[
https://issues.apache.org/jira/browse/MNG-8340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17892582#comment-17892582
]
Mateusz Gajewski commented on MNG-8340:
---------------------------------------
Is this an issue with the shade plugin or with the api it consumes?
> Staged 4.0.0-beta5 broken by maven-shade-plugin
> -----------------------------------------------
>
> Key: MNG-8340
> URL: https://issues.apache.org/jira/browse/MNG-8340
> Project: Maven
> Issue Type: Bug
> Affects Versions: 4.0.0-beta-5
> Reporter: Mateusz Gajewski
> Priority: Major
> Fix For: 4.0.0-beta-6
>
>
> Reproduction: [https://github.com/trinodb/trino/pull/23849]
>
> Project structure:
> {code:java}
> > pom.xml
> > client/trino-cli/pom.xml (parent.relativePath = ../../pom.xml)
> {code}
> maven-shade-plugin writes trino-cli dependency reduced pom to:
> {code:java}
> ${project.build.directory}/pom.xml -> client/trino-cli/target/pom.xml{code}
> The file contains:
> {code:java}
> <parent>
> <relativePath>../../../pom.xml</relativePath>
> </parent>{code}
> which correctly points to root pom.xml
>
> This worked under beta4, fails under beta5 with:
> {code:java}
> [ERROR] - [FATAL] 'parent.relativePath' points at '../../../pom.xml' but
> no POM could be found, please verify your project structure @ line 3, column
> 3 {code}
> It seems that {{parent.relativePath}} is resolved against {{client/trino-cli
> instead of client/trino-cli/target}} where pom.xml is placed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
