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

refactor(dependencies): remove unused commons-io and commons-collections4 from shenyu-admin

Closed Beginner friendly
  • Is something wrong?
#7,607 2 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

@konlue is already working on this.

Since Oct 14, 2026.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
62/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Active
Tech stack
java
Domain
build-system

Research direction

Start in shenyu-admin/pom.xml at the commons-io block (around lines 296-298) and the commons-collections4 block (around lines 186-187). Run mvn -pl shenyu-admin dependency:analyze to confirm the unused declarations. Remove commons-io now, and leave commons-collections4 until #7592 and #7593 delete the apidoc viewer. Done when the analyze run reports neither as unused and the build passes.

Written by the indexing model from the issue text.

Description

priority: medium type: dependencies type: refactor

Summary

Two Apache Commons dependencies declared in shenyu-admin/pom.xml are effectively dead and should be removed.

Evidence

  • commons-io — declared at shenyu-admin/pom.xml:296-298 (<version>${commons-io.version}</version>).
    git grep org.apache.commons.io across shenyu-admin/ (main and test) returns 0 matches → no source usage.

  • commons-collections4 — declared at shenyu-admin/pom.xml:186-187. The only two files importing org.apache.commons.collections4 are:

    • shenyu-admin/src/main/java/org/apache/shenyu/admin/controller/ApiDocController.java
    • shenyu-admin/src/main/java/org/apache/shenyu/admin/service/manager/impl/DocManagerImpl.java

    Both belong to the apidoc viewer that is being removed by #7592 / #7593. Once those land, this dependency has no consumer.

Action

  1. commons-io can be removed independently now (no source usage) — confirm with mvn -pl shenyu-admin dependency:analyze.
  2. commons-collections4 removal is gated on #7592/#7593: after the apidoc viewer is deleted, re-run mvn -pl shenyu-admin dependency:analyze to confirm it becomes an "Unused declared dependency".
  3. Remove the corresponding <dependency> blocks from shenyu-admin/pom.xml.
  4. Drop the now-orphaned <commons-io.version> property if no other module references it (cross-check git grep commons-io.version). Keep commons-collections4 in root <dependencyManagement> only if used elsewhere; otherwise drop.

Acceptance

  • mvn -pl shenyu-admin dependency:analyze reports neither as unused after cleanup.
  • Build + CI green.

Related

  • #7592, #7593 (apidoc removal, gates commons-collections4)
  • #7583 (dependency cleanup umbrella)
Dominant language
Java
Stars
8.9k
Forks
3.1k
Avg merge
2d 16h
Merged PRs (30d)
444

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

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 apache/shenyu

All issues in apache/shenyu

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.