Fixed some tooling api problems after the release... -Removed the java home validation from the tooling api consumer. We have it validated early enough anyway at the provider. Removing the validation from the consumer means we no longer drag extra dependencies to the tooling api. -Reworked some tests around the java configurability to address new deafults (e.g. the immutable system properties like the encoding) -Setting empty array of jvm opts from the tooling api now means the same as setting null: "please use the defaults". This way things will be much easier in the current development of daemon matching. It is a change in behavior but I believe a mild one and a note in the M9 release info will be enough. -Inlined one exception message for the assertion so that we avoid classloading issues.