Enabled Caching for LombokConfig Task

[CaunCaran]

The current annotations in LombokConfig are incorrect according to the javadoc, this Pullrequest is an attempt to fix it.

As stated in the Gradle javadoc https://docs.gradle.org/current/javadoc/org/gradle/api/tasks/InputFiles.html @InputFiles @input and @OutputFile have to be applied on getters instead of fields for them to be processed.

Enabling the caching reduced the build time in our project to a quarter as it also effects the caching of dependent tasks.

[codecov]

Codecov Report

Merging #525 (3aa1842) into master (11da498) will increase coverage by 0.04%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##             master     #525      +/-   ##
============================================
+ Coverage     30.54%   30.59%   +0.04%     
- Complexity      194      198       +4     
============================================
  Files           104      104              
  Lines          2668     2667       -1     
  Branches        234      234              
============================================
+ Hits            815      816       +1     
+ Misses         1786     1780       -6     
- Partials         67       71       +4     

Impacted Files	Coverage Δ
...fair/gradle/plugins/lombok/tasks/LombokConfig.java	65.00% <100.00%> (-0.58%)	⬇️
.../freefair/gradle/plugins/git/GitVersionPlugin.java	21.33% <0.00%> (+2.66%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 11da498...3aa1842. Read the comment docs.

[larsgrefer]

Annotating the java fields is sufficient, as long as there is a corresponding getter (which is generated by lombok in my case): gradle/gradle#7688

The conceptual problem with the cacheability of the task is this:
The "actual" inputs for the task are all the lombok.config files which are taken into account while determining the effective configuration. Unfortunately we don't know which config files will be used as the configuration system is quite complex: https://projectlombok.org/features/configuration Lombok will recursively traverse the file system and even allows importing other files.

[CaunCaran]

Thank you for your quick response.

We have noticed, that we can skip the lombok config generation all together since we don't have any specific configuration.
Therefore i will close this merge request as we no longer require any caching of the LombokConfig task.

[flocsy]

How did you "skip the lombok config generation"? I have similar problem: builds are very slow, even when I already had a full build and did not change anything in the java code the generateEffectiveLombokConfig tasks run on the next build. We don't even have any lombok.config file in our project.

[CaunCaran]

The easiest way is to set the System Property in your build.gradle: System.setProperty("lombok.disableConfig", "true")

But maybe there should be a configuration option to ignore external files and rely on clean build in case of external file changes.