[GitHub] beam pull request #3151: [BEAM-1663] Use stable naming strategy for ByteBudd...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/beam/pull/3151


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] beam pull request #3151: [BEAM-1663] Use stable naming strategy for ByteBudd...

[kennknowles]

GitHub user kennknowles opened a pull request:

https://github.com/apache/beam/pull/3151

[BEAM-1663] Use stable naming strategy for ByteBuddy invokers

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-] Description of pull request`
 - [ ] Make sure tests pass via `mvn clean verify`.
 - [ ] Replace `` 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](https://www.apache.org/licenses/icla.pdf).

---

This helps to coalesce related failures across multiple JVM instances, over 
time, across machines, etc.


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

$ git pull https://github.com/kennknowles/beam bytebuddy-names

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

https://github.com/apache/beam/pull/3151.patch

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

This closes #3151


commit 515c0c846c63e5a05d792ce3b8c60aaa4acdd382
Author: Kenneth Knowles 
Date:   2017-03-09T01:02:05Z

Use stable naming strategy for ByteBuddy invokers

This helps to coalesce related failures across multiple
JVM instances, over time, across machines, etc.




---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---