If you put your configuration additionally into a profile in the parent, that is
activated e.g. on the existence of the file "profiles/lombok". Then you can
simply create that in those child projects individually that use the
processor. Personally I share typically the profile's name with the one o
Thank you Anders, the `combine.children="append"` attribute applied to the
child's element does the trick.
Wonderful!
On Thu, Oct 15, 2020 at 12:54 PM Anders Hammar wrote:
> Maybe this blog post helps:
>
> https://blog.sonatype.com/2011/01/maven-how-to-merging-plugin-configuration-in-complex-p
Maybe this blog post helps:
https://blog.sonatype.com/2011/01/maven-how-to-merging-plugin-configuration-in-complex-projects/
/Anders
On Thu, Oct 15, 2020 at 12:25 PM Andres Almiray wrote:
> Hello everyone,
>
> I wonder if it's possible to define a plugin's configuration on both parent
> & child
Hello everyone,
I wonder if it's possible to define a plugin's configuration on both parent
& child in such a way that the resulting configuration is merged, first
the parent's then the child's. My use case is defining a set of annotation
processors in the maven-compiler-plugin at the parent, als
