Page History

The following applies only to Mercurial (hg) repositories. For GIT repositories, the Skara tooling provides jcheck.

The various JDK projects on OpenJDK, e.g., jdk9, use jcheck to check the content and commit message of each changeset that goes into the repo. See the jcheck page for more information about jcheck, and the OpenJDK Producing a Changeset page for the required format of commit messages.

OVERVIEW

OpenJFX is not presently enabled to use jcheck on the server, but we are working towards this as a goal. This work is tracked by JBS bug JDK-8145561. The three main benefits of using jcheck are:

...

Once you have done the above setup, you can run jcheck at any time.

To check all outgoing changesets the 'tip' changeset after you commit but before you push:

...

If you only have a single, committed but unpushed changeset:

$ hg

...

 rollback   # NOTE: this only undoes the last hg operation that modified your

...

 repo
<fix any reported white-space problems>
$ hg commit
<enter a corrected commit message>

If you have multiple changesets, or if you have done another write operation, then you will need to save off your patches and redo them, either with a new clone of the repo or by stripping the unpushed changesets from your local repo. For this reason, you should run "hg jcheck" right after each "hg commit".