beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bjchambers <>
Subject [GitHub] incubator-beam pull request #869: Remove legacy import order
Date Wed, 24 Aug 2016 00:30:58 GMT
GitHub user bjchambers opened a pull request:

    Remove legacy import order

    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`. (Even better, enable
           Travis-CI on your fork and ensure the whole test matrix passes).
     - [*] 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](

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

    $ git pull import-orders

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 #869
commit b1123417a6b55fba1560fa68096d0b5551efa960
Author: Ismaël Mejía <>
Date:   2016-08-22T15:25:32Z

    [BEAM-574] Remove log when new records have not been read yet (KafkaIO)

commit b380a677b2823897b1ecc1b903e0775d794423e0
Author: Dan Halperin <>
Date:   2016-08-23T16:59:53Z

    Closes #859

commit 9fb604d670267e2ae60ca94320a5a033b405fefb
Author: bchambers <>
Date:   2016-08-24T00:06:17Z

    Update checkstyle.xml to put all imports in one group

commit 6487fb11676e8a436a3cc40e06909d8caabec0b6
Author: bchambers <>
Date:   2016-08-24T00:27:50Z

    Optimize imports


If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message