Am 02.12.2010 04:20, schrieb David Holmes:
Exactly. The whole Eclipse problem that motivated this stemmed from the fact that they wanted a way to identify the JVM, given a "java" command, without having to launch the VM and parse some version output. This is what this simple file aims to do.
Even a simple file must be parsed anyway and additionally the referenced jvm.cfg file in a different, unsupported, non-standard format.
But I'm inclined to think that this isn't worth the effort any more, particularly as all it does is open a can of worms regarding what info different environments might want about the VM - and given the original problem that motivated this is moot for a number of reasons.
Yes, that's I wanted to saw. So if, then provide the diversity of worms complete, but reasonable grouped: - version infos - standard java options - standard javac options - -X options - -XX options - VM options -Ulf
