Java – maven – cannot activate a configuration file in a multi module project

I have encountered some difficulties in configuring our project with Maven and need some help:)

For example, I have a multi module project, modules a and B (there are about 20 other modules), but they all inherit some "root" POM

I also have a custom Maven plugin that can only be enabled for module a

The plug-in should run all modules in the same way, so I put the configuration in the root POM

The plug-in is now defined in the configuration file so that it will only be activated if I explicitly request it:

mvn test -PrunMyPlugin

If I run this command from the root directory and I run it in the directory of module a, this should work In module B, the plug-in should not run regardless of this configuration file

on the other hand

mvn test

Plug ins should never be called

I tried to use activation on a property, but it didn't work for me I try to avoid this when I need to configure plug-ins for each specific module and keep all the configurations in the root POM

Can anyone provide some simple examples of how to do this? Any help would be appreciated

Thank you in advance

Solution

Currently, Maven 2 or 3 does not support defining a profile in a parent and then activating it from a child or other profile Some stack overflow questions and answers [1] cover the details Maven's problem tracker has related function requests:

> https://issues.apache.org/jira/browse/MNG-3309 > https://issues.apache.org/jira/browse/MNG-4565 > https://issues.apache.org/jira/browse/MNG-5127

@Raghuram suggests using < plugin Management >, which is a way to do this without repeated configuration The other is to explicitly copy the configuration in each sub module that needs it

[1]：Activate different Maven profiles depending on current module?; Why can’t I activate a Maven2 profile from another profile?