You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The 'default' and 'archives' configurations are added to each project that applies the 'base' plugin (which is almost every project). They are currently still required for backward compatibility. But using them is generally discouraged.
They definitely should not be used for resolving. Thus we should deprecate that.
It will also have the positive effect that the dependencies task won't list and resolve them anymore.
And then gradle dependencies --write-locks also won't write (unnecessary) lock files for them.
The text was updated successfully, but these errors were encountered:
jjohannes
changed the title
Deprecate 'default' configuration for resolving
Deprecate 'default' and 'archives' configurations for resolving
Mar 6, 2020
jjohannes
changed the title
Deprecate 'default' and 'archives' configurations for resolving
Deprecate 'default' and 'archives' configurations for resolving and declaring dependencies
Mar 6, 2020
The 'default' and 'archives' configurations are added to each project that applies the 'base' plugin (which is almost every project). They are currently still required for backward compatibility. But using them is generally discouraged.
They definitely should not be used for resolving. Thus we should deprecate that.
It will also have the positive effect that the
dependencies
task won't list and resolve them anymore.And then
gradle dependencies --write-locks
also won't write (unnecessary) lock files for them.The text was updated successfully, but these errors were encountered: