If you received an error message, please include it and any exceptions.
We commonly need to know what platform you are on:
java -version
)uname -a
)We definitely welcome patches and contributions to grpc! Here are some guideline and information about how to do so.
In order to protect both you and ourselves, you will need to sign the Contributor License Agreement.
We follow the Google Java Style Guide. Our build automatically will provide warnings for style issues. Eclipse and IntelliJ style configurations are commonly useful. For IntelliJ 14, copy the style to ~/.IdeaIC14/config/codestyles/
, start IntelliJ, go to File > Settings > Code Style, and set the Scheme to GoogleStyle
.
If planning on making a large change, feel free to create an issue on GitHub, visit the #grpc IRC channel on Freenode, or send an email to grpc-io@googlegroups.com to discuss beforehand.
Make sure that ./gradlew build
(gradlew build
on Windows) completes successfully without any new warnings. Then create a Pull Request with your changes. When the changes are accepted, they will be merged or cherry-picked by a gRPC core developer.
The tests in interop-testing project require jetty-alpn agent running in the background otherwise they'll fail. Here are instructions on how to setup IntellJ IDEA to enable running those tests in IDE:
Step 1 must be taken, otherwise by the default JUnit Test Runner running a single test in IDE will trigger all the tests.