This message was deleted.
# community-support
s
This message was deleted.
1
v
Which level of confidence do you seek?
Or said differently, you can remove it, but you then need to use the new name without unsafe
Release notes:
See the upgrading guide if you were already using this feature in previous releases, as all
org.gradle.unsafe.configuration-cache...
properties were renamed to reflect the fact they are now fully supported.
Upgrade guide:
Configuration cache options renamed
In this release, the configuration cache feature was promoted from incubating to stable, and as such, all properties originally mentioned in the feature documentation (which had an
unsafe
part in their names, e.g.
org.gradle.unsafe.configuration-cache
) were renamed, in some cases, by just removing the
unsafe
bit.
*Incubating propertyFinalized property*`org.gradle.unsafe.configuration-cache`
org.gradle.configuration-cache
org.gradle.unsafe.configuration-cache-problems
`org.gradle.configuration-cache.problems`*
org.gradle.unsafe.configuration-cache.max-problems
org.gradle.configuration-cache.max-problems
Note that the original
org.gradle.unsafe.configuration-cache…
properties continue to be honored in this release, and no warnings will be produced if they are used, but they will be deprecated and removed in a future release.
git grep
only comes up with properties files, docs, tests, and
subprojects/core/src/main/java/org/gradle/initialization/StartParameterBuildOptions.java
where they are used as "deprecated name"
🙌 1
j
I’m aware of the migration guide, but that’s not something user will go to when upgrading their Gradle version when using our template project with such
unsafe
property set.
StartParameterBuildOptions
and deprecated names is helpful here — but I didn’t notice such deprecation message in the console. 🤔
v
They don't come yet, see the part form the upgrade guide
Last paragraph
j
Right, thanks a lot for all details, Björn!
v
You're welcome
I just share what I know, I'm just another user 🙂