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

storm-shaded-deps shades some jar files, i.e. renames the classes in those jar files, and

the internal references to those classes. Storm code should not reference the base classes.

Add a check, either in maven, or as a test case, or a shell script/python script - to confirm that no shaded classes are referenced directly.

---
Originally reported by bipinprasad, imported from: Change mvn build process to validate shaded classes are not used directly

• status: Open
  
• priority: Major
  
• resolution: Unresolved
  
• imported: 2025-01-24
  

Start by reading the Maven build configuration and running the existing build to understand how storm-shaded-deps is handled. Check the available Java references against the shaded classes, using a Maven check, test case, or shell/Python script as appropriate. Done means the build validates that Storm code does not reference shaded base classes directly.

Written by the indexing model from the issue text.