[STORM-3859] Change mvn build process to validate shaded classes are not used directly · apache/storm#7641

2022-04-27T14:40:31.000Z

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

(0 Kommentare) (0 Reaktionen) (0 zugewiesene Personen)Java (6.517 Stars) (4.149 Forks)batch import

good first issueimported-jira-issuerfe

Beschreibung

Contributor Guide

Tech Stack: java
Domain: build systemtooling
Issue Type: feature
Schwierigkeit: 3
Geschätzte Zeit: 1-2 days
Aktivitätsstatus: stale
Klarheit: mostly clear
Voraussetzungen: Maven build systemJava shading conceptsShell scripting or Python
Einsteigerfreundlichkeit: 20
Research-Richtung: 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.