opensearch-project/OpenSearch

[Feature Request] Automate detection of unused dependencies

Open

#19,364 opened on 2025年9月22日

GitHub で見る
 (2 comments) (0 reactions) (1 assignee)Java (8,123 stars) (1,505 forks)batch import
Buildenhancementgood first issue

説明

Is your feature request related to a problem? Please describe

This repository has a lot of subprojects, each with its own set of dependencies. This leads to a lot of maintenance in keeping these dependencies up to date. We use dependabot to automate updates but that does not eliminate manual work. See #19347 for a case where a dependency was unused. It would be great to automate detection of unused dependencies so they can be removed in order to reduce maintenance overhead.

Describe the solution you'd like

See #5652 for one possible solution for detecting unused dependencies

Related component

Build

コントリビューターガイド

技術スタック
java
領域
build system
Issue 種別
feature
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
3
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
1-2 days
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
blocked
明確さ期待される変更、受け入れ条件、次の手順がどれだけ明確かを示します。
clear
前提条件
Java programmingGradle or Maven build systemOpenSearch project architecture
初心者向け度初回貢献者にどれだけ取り組みやすいかを 1-100 で推定したスコアです。
35
調査方針
Review the discussion in #5652 for a potential implementation approach. Check the OpenSearch build system (likely Gradle) to understand how dependencies are declared and managed. Look at the project's build scripts (e.g., build.gradle files) to identify where unused dependencies might be detected. Consider using an existing tool like com.github.ben manes.versions or gradle dependency guard. Ensure the solution does not break existing builds and test it on a subproject like #19347.
[Feature Request] Automate detection of unused dependencies · opensearch-project/OpenSearch#19364 | Good First Issue