This section takes you through how you can help apply Java 7 project Coin features in the OpenJDK and submit patches, improving the code quality in Java itself! Any questions, comments, feedback etc please send to the Adopt OpenJDK group (if you have no luck there, try posting to the JUG leaders list).
The Adopt OpenJDK reviewers will liaise with the following sponsors to get patches into the right groups.
You should work on project Coni fixes in the following order (which is basically from safest to more difficult to prove safety).
The barrier for the OpenJDK committers to accept a patch (even one as seemingly simple as a project coin clean-up) is exceptionally high. The instructors will be checking a wide variety of conditions before your patch can be accepted. Please survey the list below and try to ensure your patch meets the quality bar.
Main focus: simple, minimal, and risk-free project coin fixes. We've listed some gotchas below:
Remember not to overlap with other efforts that are going on. If you're part of a global hack day, your instructor(s) will be co-ordinating with other teams. Fix some warnings in the source code (these are mainly under $SOURCE_CODE/jdk8_tl/jdk/src/share/classes). Depending on whether you're using the new or old build system, you'll then want to execute a build.
cd $SOURCE_CODE/ make images &> build.log tail -f build.log
./executePartialBuild.sh tail -f build.log
When the build is done you should see something in the build.log file like:
Done Processing SUBDIRS: tools java javax sun com org sunw jpda mkdemo mksample launchers linux i586 1.8.0-internal build finished: 12-04-21 19:08
NOTE: The build will be much faster the 2nd time around, it only compiles in and around the area that you have changed.
See Run jtreg tests
See Create Patches
See Submit Patches
Back to Adopt OpenJDK