Enable compilation avoidance

[jprinet]

The Gradle Enterprise extension can improve build performances by using compilation avoidance.

This feature is enabled if the compiler is hinted not to use annotation processors (<proc>none</proc>) or if all annotation processors found on the classpath are listed as part of the annotationProcessorPaths.

This PR aims to fix this. Please note that I collected all the modules for which the compilation avoidance was disabled by running locally the build on all projects with tests:
./mvnw clean install

It is then easy to spot the console output for compilation goals containing:

[WARNING] The following annotation processors were found on the classpath: [...].
Compile avoidance has been deactivated.
Please use the maven-compiler-plugin version 3.5 or above and use the <annotationProcessorPaths> configuration element to declare the processors instead.
If you did not intend to use the processors above (e.g. they were leaked by a dependency), you can use the <proc>none</proc> option to disable annotation processing.

[gsmet]

I need to have a look at that but we probably need to adjust how the version are defined as they need to be consistent with the one in the BOM.
Don't change anything, I'll think about it and talk to @aloubyansky too.

[jprinet]

Yes, there are some duplications but I didn't want to introduce an even more complex change.

[gsmet]

Hey @jprinet ,

What sort of benefits would this one have? I'm asking because it's quite intrusive and also things could be easily missed in the future.

For now, I haven't included this work in the big Build cache PR.

[jprinet]

What sort of benefits would this one have? I'm asking because it's quite intrusive and also things could be easily missed in the future.

You can find the details in the documentation there @gsmet
Basically, running compilation only when it is strictly necessary (ABI change in dependencies).

The benefit then depends on the type of change, it is difficult to estimate. The gain is expected to happen on the compilation goal, subsequent goals may also benefit if recompiling change their inputs.

[gsmet]

@jprinet FYI, I plan to revisit this once the new annotation processor is in.

The Panache annotation processor is also gone so it should simplify things even further. I'll start from your commit and simplify things from there.

[jprinet]

To be honest I am not happy with the changeset but I could not find a way to set it programmatically.

[cescoffier]

@gsmet Did you apply your new approach?

[cescoffier]

@ping @gsmet