Breaking change in 0.23.0?
See original GitHub issueI’ve just picked up the new version of your library and we now get the following error when running useLatestVersions
:
Could not set unknown property 'resolutionStrategy' for task ':dependencyUpdates' of type com.github.benmanes.gradle.versions.updates.DependencyUpdatesTask.
If we change our gradle config from dependencyUpdates.resolutionStrategy
to
dependencyUpdates.resolutionStrategyAction
things work as before.
Just wondering if this was an intentional change or not before we roll this fix out across our projects?
Issue Analytics
- State:
- Created 4 years ago
- Comments:17 (12 by maintainers)
Top Results From Across the Web
Vector releases
The Vector team is pleased to announce version 0.23.0! Be sure to check out the upgrade guide for breaking changes in this release....
Read more >Release Notes — PyMedPhys
0.23.0 #. Breaking Changes#. Removed jupyter , bundle , and app sub commands from the CLI. Removed the gui and jupyter optional extra...
Read more >Versions Transformation
It can be useful for automatically allowing certain kinds of changes based on the version difference (e.g. allow breaking changes in a new...
Read more >Version 0.22.0 (December 29, 2017)
This is a major release from 0.21.1 and includes a single, API-breaking change. We recommend that all users upgrade to this version after...
Read more >Release 0.23.0 (possibly to be 1.0.0) - Announce - Discuss
0, but finally 0.23.0 is here. It comes with quite a long list of changes, some of them breaking, since I've been reviewing...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Released version 0.24.
The direct assignment of the
dependencyUpdates.resolutionStrategy
property is supported again, but will issue a deprecation warning. Instead of an explicit=
, prefer the DSL style of an assignment method.This deprecated usage will show up as a build warning like other Gradle feature deprecations, where a detailed message is shown when running with
--warning-mode=all
.Sorry, this was unintentional. I’ll have a fix out by the end of the weekend.
cc @ghus-raba