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

Description

Contributor guide

Tech stack

java

Domain

build systemtooling

Issue type

feature

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

3

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

1-2 days

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

stale

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

mostly clear

Prerequisites

Maven build systemJava shading conceptsShell scripting or Python

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

20

Research direction

Investigate the storm shaded deps module's pom.xml to understand which classes are shaded. Consider implementing a Maven enforcer rule or a unit test that scans class files for references to the original (unshaded) class names. Look for existing similar checks in the Storm repository or other Apache projects.