gnodet commented on PR #912: URL: https://github.com/apache/maven/pull/912#issuecomment-1352250822
Some ITs failures are caused by the changes in the new reactor reader. The current behaviour is to allow inter-module dependencies at the `compile` phase. I wonder how this is actually valid ? For example some plugins do modify the _content_ of the artifacts at package phase, such as the `maven-shade-plugin` which can be used to rewrite classes. So the output of the compile phase is not always something that can be consumed. While I do agree that `mvn verify` should work, those tests kinda imply the `mvn compile` should always work, which I think is wrong. -- 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]
