[
https://issues.apache.org/jira/browse/MNG-7629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17647709#comment-17647709
]
ASF GitHub Bot commented on MNG-7629:
-------------------------------------
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.
> Revert MNG-6118 and provide a better solution for it
> ----------------------------------------------------
>
> Key: MNG-7629
> URL: https://issues.apache.org/jira/browse/MNG-7629
> Project: Maven
> Issue Type: Task
> Reporter: Guillaume Nodet
> Assignee: Guillaume Nodet
> Priority: Major
> Fix For: 4.0.0-alpha-4
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
