Skip to content
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

Closed
ghale opened this issue Jan 13, 2023 · 5 comments
Closed

Deprecate org.gradle.cache.cleanup property #23533

ghale opened this issue Jan 13, 2023 · 5 comments
Assignees
Labels
a:chore Minor issue without significant impact
Milestone

Comments

@ghale
Copy link
Member

ghale commented Jan 13, 2023

Now that we have this configurable via dsl, we want to remove the magic system property.

@ghale ghale added the a:chore Minor issue without significant impact label Jan 13, 2023
@ghale ghale added this to the 8.1 RC1 milestone Jan 13, 2023
@ghale ghale self-assigned this Jan 13, 2023
@ThadHouse
Copy link
Contributor

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
Copy link
Member

big-guy commented Feb 13, 2023

#23854

@big-guy big-guy closed this as completed Feb 13, 2023
@ThadHouse
Copy link
Contributor

@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.

@ghale
Copy link
Member Author

ghale commented Feb 13, 2023

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?

@ThadHouse
Copy link
Contributor

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
a:chore Minor issue without significant impact
Projects
None yet
Development

No branches or pull requests

3 participants