So something like the following if all configuration is managed via a
pluginMangement section;
org.apache.maven.plugins
maven-enforcer-plugin
3.0.0-M2
alpha
enforce
I agree that John's solution is more how Maven is expecting you to do things in
this case.
But it is also more verbose in the submodules and it forces you to repeat
yourself (I really like the DRY principle), since you basically have to
redefine rules.
For me it depends how much you want to man
IMO John's solution, or something similar, is the Maven Way. Any solution
involving profiles is bad and should be avoided at all costs.
/Anders
On Fri, Aug 14, 2020 at 10:53 AM John Patrick
wrote:
> I would do the following snippet, not sure if phase is needed, not
> sure if it should be plugin
I would do the following snippet, not sure if phase is needed, not
sure if it should be pluginManagement, but i tend to put all
configuration in pluginManagement then only the usage in plugins.
For the query, from what I'm aware I used the same id of default, it
will override that execution from m
You could split your config into multiple executions and define a custom skip
property for each execution.
In a submodule you could then skip the executions you don't want (or vice
versa) by adding the respective properties.
Skipping all enforcer rules (e.g. for a "quick" local run) is more compl
I am using a maven-enforcer plugin in a multi-module maven project. Let's
say my project structure is like below
main
- query
- storage
My enforcer plugin in main pom looks like below
org.apache.maven.plugins
maven-enforcer-plugin
