Convergence inconsistent resolution
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 123
- Forks
- 45
- PR merge metrics
- No merged PRs in 30d
Description
the resolver seems to inconsistently resolve transitive, dependencies that are both optional and non optional. For instance
- resolving
io.vertx:vertx-stomp:3.1.0resolves toio.vertx:vertx-auth-common:3.1.0 - resolving
io.vertx:vertx-auth-common:3.1.0resolves to a list that containsio.vertx:vertx-core:jar:3.1.0
the io.vertx:vertx-core:jar:3.1.0 does not appear in the first resolution because it is filtered by an optional dependency like io.vertx:vertx-lang-groovy:3.1.0 although it should be retained as this is a direct dependency of io:vertx-auth-common:3.1.0
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
The issue names no source files, tests, or entry points. Start by reproducing the two resolution examples for the listed Vert.x dependencies and trace how optional dependencies are filtered; done means the direct vertx-core dependency remains in the transitive resolution while unrelated optional dependencies stay filtered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100