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 'default' and 'archives' configurations for resolving and declaring dependencies #12379

Closed
jjohannes opened this issue Feb 28, 2020 · 1 comment
Assignees
Labels
Milestone

Comments

@jjohannes
Copy link
Contributor

jjohannes commented Feb 28, 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.

@jjohannes jjohannes added this to the 6.3 RC1 milestone Feb 28, 2020
@jjohannes jjohannes self-assigned this Mar 6, 2020
@jjohannes jjohannes changed the title Deprecate 'default' configuration for resolving Deprecate 'default' and 'archives' configurations for resolving Mar 6, 2020
@jjohannes jjohannes changed the title Deprecate 'default' and 'archives' configurations for resolving Deprecate 'default' and 'archives' configurations for resolving and declaring dependencies Mar 6, 2020
@ljacomet
Copy link
Member

ljacomet commented Mar 9, 2020

Fixed through #12460

@ljacomet ljacomet closed this as completed Mar 9, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants