Alexey Varlamov wrote:
> [snip]
>> > > What are you concerned about wasting? It will take longer for
>> sure, but
>> > > 'java -version' doesn't need to be super fast (it prints to the
>> console
>> > > and quits). In addition, we should consider gathering version
>> > > information from the cla
[snip]
> > What are you concerned about wasting? It will take longer for sure, but
> > 'java -version' doesn't need to be super fast (it prints to the console
> > and quits). In addition, we should consider gathering version
> > information from the class library code too, i.e. to show each mo
hi all,
please do not forget there is a *-showversion* which prints version
and continues ;-)
On 10/13/06, Geir Magnusson Jr. <[EMAIL PROTECTED]> wrote:
Leo Li wrote:
> On 10/13/06, Geir Magnusson Jr. <[EMAIL PROTECTED]> wrote:
>>
>>
>>
>> Tim Ellison wrote:
>> > Leo Li wrote:
>> >> Due to cur
Leo Li wrote:
On 10/13/06, Geir Magnusson Jr. <[EMAIL PROTECTED]> wrote:
Tim Ellison wrote:
> Leo Li wrote:
>> 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 v
On 10/13/06, Geir Magnusson Jr. <[EMAIL PROTECTED]> wrote:
Tim Ellison wrote:
> Leo Li wrote:
>> 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 sup
Tim Ellison wrote:
Leo Li wrote:
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
Leo Li wrote:
> 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 thin
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 sugg
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
This issue was discussed several times already. Seems that the set of
'standard' options should be defined for Harmony VM's and describe
somewhere.
But nobody do it yet :)
thanks, Vladimir
On 10/11/06, Tony Wu <[EMAIL PROTECTED]> wrote:
I encounter an error[1] when run java -version with IBM
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 19
11 matches
Mail list logo
