AzazelSensei opened a new pull request, #843:
URL: https://github.com/apache/maven-shade-plugin/pull/843
Following this checklist to help us incorporate your
contribution quickly and easily:
- [x] Your pull request should address just one issue, without pulling in
other changes.
- [x] Write a pull request description that is detailed enough to understand
what the pull request does, how, and why.
- [x] Each commit in the pull request should have a meaningful subject line
and body.
Note that commits might be squashed by a maintainer on merge.
- [x] Write unit tests that match behavioral changes, where the tests fail
if the changes to the runtime are not applied.
This may not always be possible but is a best-practice.
- [x] Run `mvn verify` to make sure basic checks pass.
A more thorough check will be performed on your pull request automatically.
- [ ] You have run the integration tests successfully (`mvn -Prun-its
verify`).
- [x] I hereby declare this contribution to be licenced under the [Apache
License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0)
- [ ] In any other case, please file an [Apache Individual Contributor
License Agreement](https://www.apache.org/licenses/icla.pdf).
Maven 4 treats a missing parent relativePath as `..`. The reduced POM
sits next to the project POM, so that default walks into a file that is
not the parent and reports a cycle.
I only keep a real relativePath when it actually points at the parent
POM. Otherwise I write an empty one so Maven goes to the repository.
Local-only parents still keep their path.
`PomWriterRelativePathTest.emptyRelativePathIsWritten` fails on current
master (the empty path is dropped). It passes here.
Fixes #813
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
