beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From kennknowles <>
Subject [GitHub] incubator-beam pull request #1205: [BEAM-822] Add meaningless annotation to ...
Date Thu, 27 Oct 2016 03:56:28 GMT
GitHub user kennknowles opened a pull request:

    [BEAM-822] Add meaningless annotation to to avoid spurious rebuilds

    Be sure to do all of the following to help us incorporate your contribution
    quickly and easily:
     - [x] Make sure the PR title is formatted like:
       `[BEAM-<Jira issue #>] Description of pull request`
     - [x] Make sure tests pass via `mvn clean verify`. (Even better, enable
           Travis-CI on your fork and ensure the whole test matrix passes).
     - [x] Replace `<Jira issue #>` in the title with the actual Jira issue
           number, if there is one.
     - [x] If this contribution is large, please file an Apache
           [Individual Contributor License Agreement](
    Together with #1204 this will eliminate spurious rebuilds of the Java SDK.
    R: @lukecwik  and @swegner does this violate anything you had in mind for `build-tools`?
It could also go in the core SDK, I suppose. It is nice to put it somewhere that users will
not depend on it. (so if they obey IWYU it is not part of the API)

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

    $ git pull package-info-annotations

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 #1205
commit 6d4a2635199550fa361c470e788ff7f7be4084b0
Author: Kenneth Knowles <>
Date:   2016-10-27T03:51:51Z

    Add meaningless annotation to to avoid spurious rebuilds


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