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.

Sign up for GitHub

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

Jump to bottom

Fully remove deepExtract from Gradle #13490

Closed
4 tasks
HonkingGoose opened this issue Jan 11, 2022 · 1 comment
Closed
4 tasks

Fully remove deepExtract from Gradle #13490

HonkingGoose opened this issue Jan 11, 2022 · 1 comment
Assignees
@rarkins
Labels
breaking Breaking change, requires major version bump manager:gradle Gradle package manager priority-3-medium Default priority, "should be done" but isn't prioritised ahead of others status:in-progress Someone is working on implementation type:refactor Refactoring or improving of existing code

Comments

@HonkingGoose
Copy link
Collaborator

HonkingGoose commented Jan 11, 2022 •
edited by viceice
Loading

Describe the proposed change(s).

Relevant part of quote by head maintainer @rarkins:

We are planning to remove Gradle deep functionality in a future major release, perhaps the next one. ...snip...

Todo:

  • Warn user ahead of time in the docs about deprecation, see docs: deprecate deepExtract #13487
  • Remove deepExtract functionality from the renovate
  • Migrate deepExtract config
  • Probably some other things that I'm forgetting about now

Feel free to edit the todo's to match the work that needs to be done. 😉
@HonkingGoose HonkingGoose added priority-3-medium Default priority, "should be done" but isn't prioritised ahead of others type:refactor Refactoring or improving of existing code breaking Breaking change, requires major version bump manager:gradle Gradle package manager status:requirements Full requirements are not yet known, so implementation should not be started labels Jan 11, 2022
@rarkins rarkins mentioned this issue Mar 3, 2022
Merged
6 tasks
@rarkins rarkins self-assigned this Mar 3, 2022
@rarkins rarkins added status:in-progress Someone is working on implementation and removed status:requirements Full requirements are not yet known, so implementation should not be started labels Mar 3, 2022
@rarkins
Copy link
Collaborator

rarkins commented Mar 4, 2022

Closed by #14490

@rarkins rarkins closed this as completed Mar 4, 2022
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 4, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@rarkins rarkins

Labels
breaking Breaking change, requires major version bump manager:gradle Gradle package manager priority-3-medium Default priority, "should be done" but isn't prioritised ahead of others status:in-progress Someone is working on implementation type:refactor Refactoring or improving of existing code
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@rarkins @HonkingGoose