Background

The enable-clover profile triggers at the verify stage which results in compilation failure if any code generation step in performed in magnolia code, because of duplicate classes being discovered by clover plugin.

The detailed explanation of the error can be found at https://openclover.org/doc/manual/4.2.0/kb--duplicate-class-errors-jaxb-or-jaxb2-plugin.html

As the test framework uses the grpc code generator plugin a similar issue to the jaxb2 code generator is found.

Currently, the test framework as a workaround overrides the enable-clover profile in the parent pom, by ensuring that the clover plugin gets triggered before the code generator plugin, that is clover plugin gets triggered at process-sources phase whereas the code generator at generate-resources phase.

This change in profile configuration should be pushed into the super parent pom of magnolia.