This message was deleted.
# develocity
s
This message was deleted.
a
Hi @Jörgen Andersson! I will have a look into it and will get back to you.
Just to make sure that I understood you correctly. You have
<annotationProcessorPaths>
configured, but still getting a message that it needs to be configured?
j
@Alexey Venderov Actually, I get the same message both with and without the
<annotationProcessorPaths>
configuration. And I know the configuration is in the right place, since if I switch to
<proc>none</proc>
I get a compilation error due to Lombok annotation processing not taking place. The strangest part I think is that I get the warning and still get the "Loaded from the build cache..." message. And in the build scan I can see that the build cache was indeed used.
a
OK. Thank you for the additional details. I will have a look into this issue.
n
@Jörgen Andersson When you added the annotation processor to the
annotationProcessorPaths
, did you also remove it from the other configuration?
j
@no I don't understand. Which "other configuration" are you thinking of?
n
Where was it originally?
j
Nowhere. But it still used the cache and had the exact same printout in the log. That was what caught my eye. I thought it would not use the cache, but it did.
n
The warning is about compile avoidance not about caching. The annotation processor needs to be removed from the original compile configuration and replaced with the annotation processor paths.
j
I see. I didn't realise compile avoidance and caching are different things when building with Maven. However, I didn't find any original annotation processor configuration more than having the Lombok jar on the classpath. I'll guess I'll have another look tomorrow. Thanks for pointing me in the right direction.
a
@Jörgen Andersson I've created a small project that shows the configuration of the GE Maven Extension together with Lombok: https://github.com/c00ler/ge-maven-extension-lombok
If you run it via
./mvnw clean verify
you should not see any warnings
If you try to comment out the
maven-compiler-plugin
configuration, you should see the same warning as in your example
j
Great thank you. I'll compare it to what I have when back at work tomorrow.
👍 1
It turned out the build was using the default version of maven-compiler-plugin, which was way too old.
annotationProcessorPaths
configuration is ignored in versions pre 3.5. Upgrading to a newer version made the configuration work as expected.
👌 2
n
Thanks for the update Jorgen! Glad to hear it is working 🙂
a
Awesome!