[
https://issues.apache.org/jira/browse/BEAM-2080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17546516#comment-17546516
]
Kenneth Knowles commented on BEAM-2080:
---------------------------------------
This issue has been migrated to https://github.com/apache/beam/issues/18378
> Add custom maven enforcer rules to catch banned classes and dependencies
> ------------------------------------------------------------------------
>
> Key: BEAM-2080
> URL: https://issues.apache.org/jira/browse/BEAM-2080
> Project: Beam
> Issue Type: Improvement
> Components: build-system
> Affects Versions: Not applicable
> Reporter: Vikas Kedigehalli
> Priority: P3
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The maven enforcer plugin standard rules aren't sufficient to catch certain
> issues like:
> * An artifact built as an uber/bundled jar (usually with shade plugin)
> including banned classes.
> * An artifact pom that depends on banned dependencies. (bannedDependencies
> rule provided by enforcer plugin doesn't work always because it doesn't look
> at the dependency-reduced-pom generated by shade plugin)
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
