-
Notifications
You must be signed in to change notification settings - Fork 425
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ProguardTask is incompatible with the configuration cache #254
Comments
Hi @autonomousapps ! Thanks for the report. We'd be very happy to accept a PR that fixes this! |
@mrjameshamilton have you had a chance to take a look at the PR I filed 11 days ago? |
It seems this was released. Which version was it included in? (Looks like 7.3.0) Can this issue be closed? |
Hi @runningcode ! #258 doesn't add support for configuration cache, it simply marks the task with |
See https://docs.gradle.org/7.5-rc-1/userguide/configuration_cache.html
Running an instance of
ProguardTask
with the configuration cache on results in a failure. For example:And here are the usages, extracted from the stacktraces in the HTML report:
at proguard.gradle.ProGuardTask.extendClassPath(ProGuardTask.java:1591)
at proguard.gradle.ProGuardTask.getConfiguration(ProGuardTask.java:1486)
These usages are basically
Where it is
getProject()
that is "illegal" to call, at execution time, with configuration cache on.I am open to PRing a fix for this, but I wanted to open an issue first to see what the appetite would be for an external contribution.
The text was updated successfully, but these errors were encountered: