Page History

...

Gradle gives helpful output during execution of the number of tests completed and the number skipped without dumping out lots of output to the console (unless you opt for --info). Also, once the tests complete, an HTML report is dumped to the project's build/reports/test directory (for example, modules/base/build/reports/test):

For the sake of performance, most of the tests are configured to run in the same VM. However some tests by design cannot be run in the same VM, and others cannot yet run in the same VM due to bugs or issues in the test. In order to improve the quality of the project we need to run as many tests as possible in the same VM. The more tests we can run on pre-integration the less likely we are to see failures leak into master. Being able to run 20,000 tests in a minute is extremely useful, but not possible, unless they run in the same VM. Something to keep in mind.

The last of the basic tasks you might want to accomplish is the generation of javadoc. This is done by invoking the javadoc task. NOTE: At present there is a bug where gradle javadoc will fail, but gradle :javadoc succeeds. There really isn't much to say about the generation of javadoc, other than it works .

Unique Challenges of Working on the JDK

...