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

Put back excluded configurations to dependency locking #2743

Closed
jonatan-ivanov opened this issue Aug 12, 2021 · 0 comments
Closed

Put back excluded configurations to dependency locking #2743

jonatan-ivanov opened this issue Aug 12, 2021 · 0 comments
Assignees
@jonatan-ivanov
Labels
build A change in our build-system type: task A general task
Milestone
1.6.11

Comments

@jonatan-ivanov
Copy link
Member

The resolveAndLockAll task is used to generate/update dependency lock files. Since gradle used to create a file per project per configuration, some configurations were excluded to reduce the number of files. Gradle now supports a single file per project so there is no need to exclude configurations anymore.
@jonatan-ivanov jonatan-ivanov added type: task A general task build A change in our build-system labels Aug 12, 2021
@jonatan-ivanov jonatan-ivanov added this to the 1.6.11 milestone Aug 12, 2021
@jonatan-ivanov jonatan-ivanov self-assigned this Aug 12, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jonatan-ivanov jonatan-ivanov

Labels
build A change in our build-system type: task A general task
Projects
None yet
Milestone
1.6.11
Development

No branches or pull requests
1 participant
@jonatan-ivanov