You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm actively using this plugin and we have move than 1k modules in the project. Each module has its own whitelisted dependencies which I have to add to dependencyAnalysis -> exclude block. It would be nice to have one whitelist file with all modules and all excludes and avoid using this dependencyAnalysis block in each module. What are recommendations here?
Example of current usage:
// root build script
dependencyAnalysis {
issues {
// "all" runs against EVERY module
all {
onUnusedDependencies { ... }
...
}
// "project" runs against just the specified project
project(':lib') {
onUnusedDependencies { ... }
...
}
}
}
and you can do that for each module separately if you need to. Note that global behavior can be defined in all{}, and anything more specific will take precedence over the global behavior.
I'm actively using this plugin and we have move than 1k modules in the project. Each module has its own whitelisted dependencies which I have to add to dependencyAnalysis -> exclude block. It would be nice to have one whitelist file with all modules and all excludes and avoid using this dependencyAnalysis block in each module. What are recommendations here?
Example of current usage:
module1: build.gradle.kts
Nice to have:
unused-deps-whitelist.txt
The text was updated successfully, but these errors were encountered: