apache / apache/lucene

fail the build on unused third party jars [LUCENE-4017]

Open
#5,090 0 comments 0 reactions 0 assignees View on GitHub
legacy-jira-priority:Major tool:build type:task
Dominant language
Java
Stars
3.6k
Forks
1.4k
Avg merge
2d 11h
Merged PRs (30d)
88

Description

#4884 removed 4 useless jars from benchmark/lib.

How many others do we have in this boat?

Can't we do something like http://sixlegs.com/blog/java/depfind.html
on each module, and if there is no path thru the dependency graph from
its build/xyz.jar to one in lib/, then fail (with a way to have exceptions
for only-reflected stuff)

---
Migrated from [LUCENE-4017](https://issues.apache.org/jira/browse/LUCENE-4017) by Robert Muir (@rmuir)

Contributor guide

Open the contributing guide

Research direction

Start by auditing benchmark/lib and the lib directories for each module, then trace each module's build/xyz.jar dependencies as described. Clarify how dependency-graph failures and reflection-only exceptions should be represented before implementation; done means unused jars are detected and intentional exceptions do not fail the build.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
build-system
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.