Hi all I've been having some issues with plugins that run out of lifecycle, or fork the lifecycle. For example
mvn org.openrewrite.maven:rewrite-maven-plugin:4.22.2:run -Drewrite.activeRecipes=org.openrewrite.java.cleanup.NoPrimitiveWrappersForToStringOrCompareTo This fails on one of my modules that depend on a previous module having progressed to the "prepare-package" phase. I've always assumed that having a dependency on another module means requiring that the module reach the "package" phase, if it's in the same reactor, or the "install" phase if it's not. Question 1: Is this an unreasonable assumption? Is there a convention to be followed here? Another older project that seems to have stumbled over legal issues is the macker-maven-plugin. It allows you to shape your package architecture with rules about who can import what. The last work on this project was a pull request to not fork https://github.com/andrena/macker-maven-plugin/pull/6 I didn't used to have trouble with forking plugins, but recently I implemented https://mapstruct.org/ Mapstruct is an annotation processor for mapping objects. It seems annotation processors may only run once so as to guarantee the reliability of their outputs? With a forking plugin this rule is broken. I have to skip over my mapstruct project when running either rewrite-maven-plugin or macker-maven-plugin. Question 2: Is this a problem with my project structure, with the plugins Im trying to run, with the mapstruct project itself, or with Maven? Thanks, Delany
