Transitive optional dependencies resolution issue
Open
Nobody has claimed this yet.
bug
enhancement
- Dominant language
- Java
- Stars
- 123
- Forks
- 45
- PR merge metrics
- No merged PRs in 30d
Description
It seems that optional=true dependencies that are transitively added force the resolution of the optional dependencies, e.g
vertx-junit5 -> vertx-rx-java2 -> vertx-micrometer-metrics (optional=true)
resolves vertx-micrometer-metrics jar
It can be reproduced by adding vertx-junit5 in the full stack json file and call resolve.
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 with the full stack JSON file and reproduce the issue by adding vertx-junit5, then call resolve. Trace the transitive dependency resolution and verify that the optional vertx-micrometer-metrics dependency is not resolved or included when it is marked optional.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100