[
https://issues.apache.org/jira/browse/MSHADE-387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17339367#comment-17339367
]
Shahim Essaid commented on MSHADE-387:
--------------------------------------
I rearranged the shading project to be a child of a new aggregating project. I
also made my shading project inherit from this new aggregating project which in
turn inherits from the original parent POM. This solved the issue of having the
incorrect relativePath element but I think there is some bug with the
relativePath calculation.
> relativePath added in the reduced POM when POM and parent POM do not have
> relativePath
> --------------------------------------------------------------------------------------
>
> Key: MSHADE-387
> URL: https://issues.apache.org/jira/browse/MSHADE-387
> Project: Maven Shade Plugin
> Issue Type: Bug
> Affects Versions: 3.2.4
> Environment: Windows and Linux, Java 11, Maven 3.6.3
> Reporter: Shahim Essaid
> Priority: Major
>
> I'm a new user of the plugin. I have a project that has a -SNAPSHOT parent
> resolved from a remote repository. The generated reduced POM has the
> following for the parent:
> <relativePath>../pom.xml/pom.xml</relativePath>
> and I'm not able to understand why this is occurring so I'm assuming it is a
> bug. It causes build warnings for projects using the deployed shaded
> artifact. Neither the parent or the project's POMs have a relative path
> entry. I tried a build on a different machine and the same results.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
