Hi, I'm working on a multiple modules project, and encountering an issue like this one https://issues.apache.org/jira/browse/MENFORCER-168 <https://issues.apache.org/jira/browse/MENFORCER-168>. I dig into the implementation of the enforcer plugin, and found that EnforceMojo is bound to the default phase validate. If I understand correct, the phase validate chosen was to meet a common usage that we can check the project whether have any constraint violations or not in an early stage, aka before compile / package / install / deploy. Then I'd recommend that we achieve the same goal in a multiple modules project build. This could be helpful and ease people who has issue like https://issues.apache.org/jira/browse/MNG-3283 <https://issues.apache.org/jira/browse/MNG-3283>.
Issue link: https://issues.apache.org/jira/browse/MENFORCER-304 <https://issues.apache.org/jira/browse/MENFORCER-304> PR: https://github.com/apache/maven-enforcer/pull/35 <https://github.com/apache/maven-enforcer/pull/35> Need your feedback! Related issues: https://issues.apache.org/jira/browse/MNG-3283 <https://issues.apache.org/jira/browse/MNG-3283> https://issues.apache.org/jira/browse/MENFORCER-42 <https://issues.apache.org/jira/browse/MENFORCER-42> https://issues.apache.org/jira/browse/MENFORCER-168 <https://issues.apache.org/jira/browse/MENFORCER-168> Thanks Zhenlei Huang
smime.p7s
Description: S/MIME cryptographic signature
