[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 留言) (0 反應) (0 負責人)Java (6,517 star) (4,149 fork)batch import

good first issueimported-jira-issuerfe

描述

貢獻者指南

技術棧: java
領域: build systemtooling
議題類型: feature
難度: 3
預計時間: 1-2 days
活動狀態: stale
清晰度: mostly clear
前置要求: Maven build systemJava shading conceptsShell scripting or Python
新手友善度: 20
研究方向: 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.