Testing the Code Prior to Pushing

Developers are expected to test their code prior to integrating it to avoid breaking the build or otherwise impacting other developers with badly broken code. At a minimum, developers must run the unit tests for their area, and verify that Ensemble8 runs. If you are making interface changes or other potentially broad changes, you need to run a "clean" build. For example:

    bash gradlew clean sdk apps test

For most developers these tests are enough but for even better coverage:

   bash gradlew -PFULL_TEST=true -PUSE_ROBOT=true test 

Committing the Code into the Repository

For the mainline GIT repo on https://github.com/openjdk/jfx the Skara tooling will format the commit message for you so that you don't need to do it manually.

The following applies to Mercurial repositories.

All commits require an associated JBS bug. The commit message must use the following template as described on the OpenJDK Producing a Changeset page.

<bugid>: <synopsis-of-symptom>
Summary: <summary-of-code-change>    (optional)
Reviewed-by: <reviewer>+             (must be OpenJDK id)
Contributed-by: <contributor-email>  (optional, used when applicable)

Note that you use the 7-digit bug ID excluding the "JDK-" prefix.

Developers are strongly encouraged to use jcheck to verify the format of a changeset prior to pushing any changeset.