[STORM-3859] Change mvn build process to validate shaded classes are not used directly

Repository metrics

Stars

6,517 stars (6,517 stars)

PR merge metrics

PR metrics pending (PR metrics pending)

Description

Contributor guide

Research direction

Identify shaded classes by examining the Maven shade plugin configuration and find all imports of those classes in the source code. Then implement a validation check, either as a Maven plugin execution, a unit test, or a script that fails the build if any direct usage is found.

Tech stack

java

Domain

build system

Issue type

Feature

DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.

2

Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.

Half day

Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.

Active

ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.

Clear

Prerequisites

JavaMaven

Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.

60