nebula-plugins / nebula-plugins/gradle-dependency-lock-plugin
generateGlobalLock always includes transitives, by default and even when includeTransitives=false
Open
Nobody has claimed this yet.
- Dominant language
- Groovy
- Stars
- 303
- Forks
- 46
- PR merge metrics
- No merged PRs in 30d
Description
@rpalcolea Seems like a regression issue introduced with v14.1.0, rather than an intentional change?
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 generateGlobalLock implementation and checking how the includeTransitives option is handled. Reproduce the behavior with includeTransitives=false and compare it with the behavior introduced in v14.1.0. Done means the option no longer includes transitive dependencies when disabled, with a regression test covering that case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- groovy
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100