-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Deprecate org.gradle.cache.cleanup property #23533
Comments
Is there a way to deprecate properties? We were the ones that originally added that property, and we're fine with it being removed from newer versions, as long as it doesn't error out if that property exists on newer versions. We need to be able to support both newer and older versions of Gradle on the same system, and since that property only works if its globally set, newer versions of gradle can't error if its found. |
@big-guy That is a problem. Its a global flag, and our builds need to support a mix on both Gradle 7 and Gradle 8. That PR will mean that gradle 8 will always print out a deprecation warning no matter what, with no way to solve it. |
I think you might have misunderstood the instructions that PR adds to the upgrade guide. You can continue to have the property in gradle.properties as long as you also set it via the DSL (either to disable it or to some other value). This allows you to use the property for older versions of Gradle, but avoid the deprecation warning in Gradle 8.1+. Does that make sense? Does that resolve your problem, or am I misunderstanding? |
If you have the dsl property, it won't print the deprecation warning even if the property still exists? If thats the case thats good, its just not clear from the PR how that happens. |
Now that we have this configurable via dsl, we want to remove the magic system property.
The text was updated successfully, but these errors were encountered: