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

Excluded configurations should not be resolved #126

Closed
bigdaz opened this issue Apr 1, 2024 · 0 comments
Closed

Excluded configurations should not be resolved #126

bigdaz opened this issue Apr 1, 2024 · 0 comments
Milestone
v1.3.0

Comments

@bigdaz
Copy link
Member

bigdaz commented Apr 1, 2024

When a configuration or project is excluded from the dependency graph, we should avoid resolving that configuration altogether. The current implementation merely excludes it from the graph.
@bigdaz bigdaz added this to the v1.3.0 milestone Apr 1, 2024
bigdaz added a commit that referenced this issue Apr 1, 2024
@bigdaz
Apply the configuration filter for 'resolve-all-dependencies'
8b648a2 
Previously, excluded configurations would be excluded from the graph, but they
would still be resolved. By avoiding resolution altogether, we allow users to
exclude any unresolvable dependency configurations.

Fixes #126
@bigdaz bigdaz closed this as completed in 0fabed6 Apr 2, 2024
@bigdaz bigdaz mentioned this issue Apr 4, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
v1.3.0
Development

No branches or pull requests
1 participant
@bigdaz