jfrog / jfrog/artifactory-client-java
Groovy dependency prevents adoption
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 331
- Forks
- 163
- Avg merge
- 20h 9m
- Merged PRs (30d)
- 1
Description
The requirement for Groovy 2.0 is onerous on consumers, especially since it's not groovy-all. There are many cases where this conflicts with other versions of Groovy, e.g. trying to use this effectively in a Gradle plugin. For a library appended with "-java" it probably shouldn't require any Groovy at all, but that's another issue. But if you're going to use it, I'd recommend using the lowest possible version of groovy-all, e.g. 1.8.8.
Contributor guide
No contributing guide indexed for this repository
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
No file or test is named. Start by locating the build metadata that declares the Groovy 2.0 requirement, then compare the available dependency options and verify that the Java client remains usable with the selected Groovy version or without Groovy; done means consumers no longer face the reported version conflict.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- groovy, java
- Domain
- api, build-system
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100