apache / apache/maven-shade-plugin

[MSHADE-387] relativePath added in the reduced POM when POM and parent POM do not have relativePath

Open
#394 1 comment 0 reactions 0 assignees View on GitHub
bug priority:major
Dominant language
Java
Stars
188
Forks
103
Avg merge
16h 39m
Merged PRs (30d)
4

Description

**[Shahim Essaid](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=sessaid)** opened **[MSHADE-387](https://issues.apache.org/jira/browse/MSHADE-387?redirect=false)** and commented

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:

\../pom.xml/pom.xml\

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.

---

**Affects:** 3.2.4

Contributor guide

No contributing guide indexed for this repository

Research direction

Reproduce issue #394 with a SNAPSHOT parent resolved from a remote repository and inspect the generated reduced POM. Focus on why it contains ../pom.xml/pom.xml when neither POM declares relativePath. Done means the reduced POM no longer adds the erroneous relativePath and deployed shaded artifacts do not produce the reported build warnings.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
build-system
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.