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

Add the ability for some Configuration instances to be excluded #258

Open
mcumings opened this issue Aug 20, 2024 · 0 comments
Open

Add the ability for some Configuration instances to be excluded #258

mcumings opened this issue Aug 20, 2024 · 0 comments

Comments

@mcumings
Copy link

In our project, some Configuration instances represent references to the top of the project and are applied by convention plugin to all project modules. When building the dependency graph, the AffectedModuleDetector treats these references as dependencies, resulting in every project module being considered "affected" by all others.

Having the ability to filter configurations would allow us to specifically manage this scenario, restoring the proper function of the AffectedModuleDetector.
mcumings added a commit to mcumings/AffectedModuleDetector that referenced this issue Aug 20, 2024
@mcumings
Address Issue dropbox#258: Configuration predicate to control depende…
ab7394c 
…ncy graph creation

Adds a new configuration option to allow the consumer to provision of a
`Predicate<Configuration>` instance to customize what `Configuration` instances
should be considered when building the dependency graph.
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
No milestone
Development

No branches or pull requests
1 participant
@mcumings