Affected version
3.6.0
Bug description
Seemingly harmless, it just overrides dep from parent (with same), but this triggers something unwanted in Maven 4? And makes POM transformation fail.
Sidenote: does running shade on a POM parent (so not only packaging=pom, that use case I understand), but on POM that has submodules... does it make sense?