Due to current VMI, we have to first create a java VM through JNI_CreateJavaVM, then we can get property from functions defined by VMI. It is possible not to change current vmi design and support java -version, but we have to create and then "kill" a new java vm. So I think it quite wastes. I suggest the vmi.dll export another funciton to give out some "static" property of the java vm implementation that is no relevent to a live vm.
On 10/12/06, Geir Magnusson Jr. <[EMAIL PROTECTED]> wrote:
Tony Wu wrote: > I encounter an error[1] when run java -version with IBM VME today and > it is ok on DRLVM. I wonder how to handle these simple parameters. Is > there any decision > about that? > > [1] > [EMAIL PROTECTED]:~/harmony/workspace/trunk/deploy/jdk/jre/bin$ ./java -version > Apache Harmony Launcher : (c) Copyright 1991, 2006 The Apache Software > Foundation or its licensors, as applicable. > JVMJ9VM007E Command-line option unrecognised: -version > HMYEXEL062E Internal VM error: Failed to create Java VM > FAILED to invoke JVM. > Yes, we won't pass -version into the VM, but simply have an expectation that the VM will set a property that can be read by the launcher post VM init. geir --------------------------------------------------------------------- Terms of use : http://incubator.apache.org/harmony/mailing.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Leo Li China Software Development Lab, IBM
