beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Work logged] (BEAM-2080) Add custom maven enforcer rules to catch banned classes and dependencies
Date Thu, 07 Jun 2018 04:02:00 GMT


ASF GitHub Bot logged work on BEAM-2080:

                Author: ASF GitHub Bot
            Created on: 07/Jun/18 04:01
            Start Date: 07/Jun/18 04:01
    Worklog Time Spent: 10m 
      Work Description: stale[bot] commented on issue #2688: [BEAM-2080]: Add a custom enforcer
rule to check for banned classes.
   This pull request has been marked as stale due to 60 days of inactivity. It will be closed
in 1 week if no further activity occurs. If you think that’s incorrect or this pull request
requires a review, please simply write any comment. If closed, you can revive the PR at any
time and @mention a reviewer or discuss it on the list. Thank you for
your contributions.

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

Issue Time Tracking

            Worklog Id:     (was: 109622)
            Time Spent: 10m
    Remaining Estimate: 0h

> Add custom maven enforcer rules to catch banned classes and dependencies
> ------------------------------------------------------------------------
>                 Key: BEAM-2080
>                 URL:
>             Project: Beam
>          Issue Type: Improvement
>          Components: build-system
>    Affects Versions: Not applicable
>            Reporter: Vikas Kedigehalli
>            Assignee: Vikas Kedigehalli
>            Priority: Minor
>          Time Spent: 10m
>  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
> * 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

View raw message