Closed xehpuk closed 5 months ago
@xehpuk Appreciate you bringing this matter to our attention. We attempted to replicate it on an Android project without success. Would you be open to generating a minimal reproducible case for this issue?
Thanks.
It's not an Android project, if that helps.
Sadly, it may take time for me to construct a minimal case.
Encountered the same issue. Also a non-Android project.
Seems to be related to https://github.com/jfrog/build-info/pull/789 and by that to https://github.com/google/guava/issues/6801.
@xehpuk Which version of Gradle do you use? We had the issue when using Gradle 6.9 but the issue seems to have gone away by switching to Gradle 7.6.2.
@ViToni Gradle 6.8.1 and Java 8. 🫣
@xehpuk Maybe give Gradle 7.6.2 a try. Depending on the plugins you use this is a no-brainer. We are using Java 8 as well and our only issue was an external Gradle Saxon task which didn't define inputs/outputs properly and made Gradle nag about it... Gradle 8.x might be a different beast.
@xehpuk @ViToni Based on your inputs, we have removed Guava from the code. Version 4.33.17 has been released and includes the fix for this issue. Please feel free to use it and share your feedback.
@ViToni The project is in ultra-maintenance mode. Only touching it if I have to. 😅 @yahavi That seems to fix it for me, thanks! 🥳
Describe the bug
To Reproduce Use
org.jfrog.buildinfo:build-info-extractor-gradle:4.33.16
and build.Expected behavior Successful build.
Versions
Additional context Works with 4.33.15.