Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Groovy dependency prevents adoption

Open
#37 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
30/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Stale
Tech stack
groovy, java
Domain
api, build-system

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.

Description

stale

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.

Dominant language
Java
Stars
331
Forks
163
Avg merge
20h 9m
Merged PRs (30d)
1

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from jfrog/artifactory-client-java

All issues in jfrog/artifactory-client-java

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.