rfscholte commented on pull request #26:
URL: https://github.com/apache/maven-shade-plugin/pull/26#issuecomment-873934570


   IIUC this is caused by Maven 3 using the pom.xml of the reactor for both 
build and consume. With Maven 4 we've started to separate this, but currently 
not inside the reactor. As long as Maven can ensure that the consumer-pom won't 
introduce new reactor dependencies, it should be possible inside Maven.
   I don't think this should be solved at plugin level as there are more that 
suffer from the same issue.


-- 
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: issues-unsubscr...@maven.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Reply via email to