[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 commentaires) (0 réactions) (0 assignés)Java (6 517 stars) (4 149 forks)batch import

good first issueimported-jira-issuerfe

Description

Guide contributeur

Stack technique: java
Domaine: build systemtooling
Type d'issue: feature
Difficulté: 3
Temps estimé: 1-2 days
Statut d'activité: stale
Clarté: mostly clear
Prérequis: Maven build systemJava shading conceptsShell scripting or Python
Accessibilité débutant: 20
Direction de recherche: 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.