beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (BEAM-1062) Shade SDK based on a whitelist instead of a blacklist
Date Fri, 19 May 2017 18:44:04 GMT


ASF GitHub Bot commented on BEAM-1062:

GitHub user kennknowles opened a pull request:

    [BEAM-1062] Shade the SDK more fully; everything but a whitelist

    Be sure to do all of the following to help us incorporate your contribution
    quickly and easily:
     - [ ] Make sure the PR title is formatted like:
       `[BEAM-<Jira issue #>] Description of pull request`
     - [ ] Make sure tests pass via `mvn clean verify`.
     - [ ] Replace `<Jira issue #>` in the title with the actual Jira issue
           number, if there is one.
     - [ ] If this contribution is large, please file an Apache
           [Individual Contributor License Agreement](
    Rebased on tons of changes, including a possible fix to the xerial issue.

You can merge this pull request into a Git repository by running:

    $ git pull shade-SDK

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #3186
commit 4b74653274f92c4577a82ee1ff6584b89f03b894
Author: Kenneth Knowles <>
Date:   2016-11-30T04:06:54Z

    Shade more in the SDK; everything except a whitelist


> Shade SDK based on a whitelist instead of a blacklist
> -----------------------------------------------------
>                 Key: BEAM-1062
>                 URL:
>             Project: Beam
>          Issue Type: Improvement
>          Components: sdk-java-core
>            Reporter: Kenneth Knowles
> This is a more robust way to manage the surface of dependencies we introduce.

This message was sent by Atlassian JIRA

View raw message