nebula-plugins / nebula-plugins/gradle-dependency-lock-plugin
handleSiblingTransitives ignores filters
Nobody has claimed this yet.
- Dominant language
- Groovy
- Stars
- 303
- Forks
- 46
- PR merge metrics
- No merged PRs in 30d
Description
In a multi-module project where one module depends on another, the sibling dependencies are included in the dependencies.lock and are always locked even if the filter would exclude it.
dependencyFilter = { String group, String name, String version -> !(group = "a.b.c" && name = "foo")}
If a.b.c:foo is a sibling transitive, it will still be locked to a specific version.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the handleSiblingTransitives entry point and tracing how sibling dependencies are written to dependencies.lock. Reproduce the multi-module case with the shown dependencyFilter, then verify that a.b.c:foo is excluded from locking when the filter rejects it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- groovy
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100