Hallo Etienne,
* Etienne Gagnon wrote:
>libraries in /usr/lib/sablevm, and its executable in /usr/bin. Where
>shouls JAVA_HOME point? [rhetorical question]
Mandated by the new policy would be to point the JVM property
(System.get...) java.home to /usr/lib/sablevm. In there should be
the 'java-s
Hallo Etienne,
* Etienne Gagnon wrote:
>libraries in /usr/lib/sablevm, and its executable in /usr/bin. Where
>shouls JAVA_HOME point? [rhetorical question]
Mandated by the new policy would be to point the JVM property
(System.get...) java.home to /usr/lib/sablevm. In there should be
the 'java-s
On Mon, 2003-09-22 at 13:32, Ean Schuessler wrote:
> We want Java programs to run the interpreter using a common commandline
> and directory layout. Many Java programs rely on the JAVA_HOME layout
Well - it's abvious that we *don't want* every single program to
separately support each single JVM.
On Mon, 2003-09-22 at 13:32, Ean Schuessler wrote:
> We want Java programs to run the interpreter using a common commandline
> and directory layout. Many Java programs rely on the JAVA_HOME layout
Well - it's abvious that we *don't want* every single program to
separately support each single JVM.
We want Java programs to run the interpreter using a common commandline
and directory layout. Many Java programs rely on the JAVA_HOME layout
even though it is an ill-defined non-standard. The path of least
resistance is to formalize a definition of this standard and then tune
up the behavior of pa
We want Java programs to run the interpreter using a common commandline
and directory layout. Many Java programs rely on the JAVA_HOME layout
even though it is an ill-defined non-standard. The path of least
resistance is to formalize a definition of this standard and then tune
up the behavior of pa
Hallo Ean,
* Ean Schuessler wrote:
>> After having this discussion, because they are not 'similar enough' to
>> rely on the alternative system.
>Well, they *could be* similar enough if we specify exactly what Debian
>expects a JAVA_HOME setup to provide.
It's not the java.home or anything else. T
Dalibor Topic wrote:
I think that JAVA_HOME is quite pointless, as the only good use for it
seems to
be to locate JNI headers. It's an ill-defined ad-hoc 'standard' that isn't even
supported by Sun. Programs that rely on JAVA_HOME to be able to access
internals of the VM are inherently broken, the
Hallo Ean,
* Ean Schuessler wrote:
>> After having this discussion, because they are not 'similar enough' to
>> rely on the alternative system.
>Well, they *could be* similar enough if we specify exactly what Debian
>expects a JAVA_HOME setup to provide.
It's not the java.home or anything else. T
Dalibor Topic wrote:
I think that JAVA_HOME is quite pointless, as the only good use for it seems to
be to locate JNI headers. It's an ill-defined ad-hoc 'standard' that isn't even
supported by Sun. Programs that rely on JAVA_HOME to be able to access
internals of the VM are inherently broken, they
--- Ean Schuessler <[EMAIL PROTECTED]> wrote:
> I'm still not clear on why we cannot require every VM to provide a more
> specifically detailed version of the JAVA_HOME ad hoc standard. We
> should have a document that lists all of the $JAVA_HOME/bin/..foo..
> $JAVA_HOME/lib/..bar.. locations tha
--- Ean Schuessler <[EMAIL PROTECTED]> wrote:
> I'm still not clear on why we cannot require every VM to provide a more
> specifically detailed version of the JAVA_HOME ad hoc standard. We
> should have a document that lists all of the $JAVA_HOME/bin/..foo..
> $JAVA_HOME/lib/..bar.. locations tha
12 matches
Mail list logo
