Hello, I am using the develocity maven extension to cache a goal by defining its input and ouptut. There are some cases where the cache misses due to the change in the implementation goal (exec plugin) although the same plugin version is used. (No changes on input and ouput per the build scan comparision, only goal implementation) I cant even reproduce. Can someone please assist

A Maven build scan comparison may show a "Goal Implementation Changed" message when the fingerprint for the goal implementation changes. This fingerprint is calculated from three factors: • The Maven Version • The Develocity Extension Version • A hash of all the URLs available in the classloader that loaded the mojo in question The first two should be easily diagnosable. To diagnose the third, it is necessary to use the

develocity.goal.fingerprint

logger via the

-Dorg.slf4j.simpleLogger.log.develocity.goal.fingerprint=trace

system property. This will show the difference in the classloader URLs that are causing the fingerprint to change. You can compare the output of two goals to see which URLs have different hashes.

I ll debug it and get back to you, thank you