You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Kenneth Knowles (Jira)" <ji...@apache.org> on 2022/01/12 03:51:04 UTC
[jira] [Updated] (BEAM-2080) Add custom maven enforcer rules to catch banned classes and dependencies
[ https://issues.apache.org/jira/browse/BEAM-2080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kenneth Knowles updated BEAM-2080:
----------------------------------
This Jira ticket has a pull request attached to it, but is still open. Did the pull request resolve the issue? If so, could you please mark it resolved? This will help the project have a clear view of its open issues.
> 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.1#820001)