bazel-contrib / bazel-contrib/rules_jvm_external
Detailed dependency conflict report
Open
Nobody has claimed this yet.
help wanted
type: feature request
- Dominant language
- Java
- Stars
- 373
- Forks
- 301
- Avg merge
- 7d 17h
- Merged PRs (30d)
- 3
Description
Would it be possible to output a detailed dependency resolution conflicts that would make upgrading libraries a lot easier? Or maybe this information is already written somewhere?
As a reference this is what bazel-deps outputs for each dependency with conflict:
# duplicates in com.fasterxml.jackson.core:jackson-core fixed to 2.6.7
# - com.fasterxml.jackson.core:jackson-databind:2.6.7 wanted version 2.6.7
# - com.fasterxml.jackson.dataformat:jackson-dataformat-cbor:2.6.7 wanted version 2.6.7
# - com.fasterxml.jackson.datatype:jackson-datatype-joda:2.6.7 wanted version 2.6.7
# - com.fasterxml.jackson.module:jackson-module-scala_2.11:2.6.7.1 wanted version 2.6.7
# - io.sentry:sentry:1.5.3 wanted version 2.8.7
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 checking the resolver's existing output and whether conflict details are already persisted or logged. Reproduce a dependency conflict like the Jackson example; done means the report identifies the conflicting artifact, selected version, and each dependency's requested version.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100