Nelson Minar wrote:
>
> Folks seemed to like my list of JDK environment variables, so here's a
> second pass incorporating all the feedback I got. Steve, are the
> DO_NOT_FREE and associated variables supported in 1.1 native threads?
In some past mail from Kazuki Yasumatsu d
Folks seemed to like my list of JDK environment variables, so here's a
second pass incorporating all the feedback I got. Steve, are the
DO_NOT_FREE and associated variables supported in 1.1 native threads?
--
The followi
Nelson Minar writes:
> I'd like to make a list of all the environment variables the Blackdown
> JDK uses to change its operation. I don't think there is a
> comprehensive list anywhere. Here's what I know, can others correct
> this or add to the list? Maybe we can
Nelson Minar wrote:
>
> I'd like to make a list of all the environment variables the Blackdown
> JDK uses to change its operation.
Splendid idea! I would suggest, for comprehensiveness, your list include
all environment variables -- don't leave out CLASSPATH.
> D
JAVA_COMPILER works
Pooh Bear -- "I am just a bear of little brain"
On Fri, 28 May 1999, Nelson Minar wrote:
> I'd like to make a list of all the environment variables the Blackdown
> JDK uses to change its operation. I don't think there is a
> comprehensive list
I'd like to make a list of all the environment variables the Blackdown
JDK uses to change its operation. I don't think there is a
comprehensive list anywhere. Here's what I know, can others correct
this or add to the list? Maybe we can get it into README.linux on the
next release.
On Tue, 15 Dec 1998 [EMAIL PROTECTED] wrote:
> Ok assuming you can do 3 __where__ is the standard place for the property files
> per user per machine? I think it is best to write a software installer program
> to do this task. It would write the property file to `user.home' say and the
> main
load that file and make it
a environment settings default.
Peter
__ Reply Separator _
Subject: Re: Reading (All) Environment Variables in W95/NT
Author: summer ([EMAIL PROTECTED]) at lon-mime
Date:14/12/98 23:09
3
. I have a run time shell
> script that passes the entire environment to the JVM using a system
> property.
>
> java -Denv=`env` xenon.xsql.editor.Xsql
>
> The env produces the multiline environment variables list that we know and
> love. On running the application
rovide a batch or scripting
language! (Well I think the Macintosh does not have one. Does it? )
Pete
__ Reply Separator _
Subject: Re: Reading (All) Environment Variables in W95/NT
Author: paul ([EMAIL PROTECTED]) at lon-mime
Date:14/
as well.
Pete
__ Reply Separator _
Subject: Re: Reading (All) Environment Variables in W95/NT
Author: Gerrit.Cap ([EMAIL PROTECTED]) at lon-mime
Date:14/12/98 11:49
There is a port available of a lot of unix commands for NT called
ication that runs fine on Unix
> and I am trying to get to run perfectly on NT. I have a run time shell
> script that passes the entire environment to the JVM using a system
> property.
>
> java -Denv=`env` xenon.xsql.editor.Xsql
>
> The env produces the multiline
property.
java -Denv=`env` xenon.xsql.editor.Xsql
The env produces the multiline environment variables list that we know and
love. On running the application the program looks for the value of system
property called `env'. Hence the JVM gets the entire environment. I have
source code
Nathan Meyers wrote:
>
> A little bit of shell or perl (or name-your-favorite-command-interpreter)
> programming could give you a script that would construct a Java
> command-line containing all of the environment variables as "-D..."
> options. I've attached a p
rpreter)
programming could give you a script that would construct a Java
command-line containing all of the environment variables as "-D..."
options. I've attached a perl script that'll send a Java command line to
stdout; with a little modification, it could execute the line inst
them into
the System properties list via the -D option on the commandline).
Java 1.1 does not allow a java program to read system environment
variables since they are dependent of the plattform. Hence deprecation
of System.getenv()
--
Jan-Henrik Haukeland
Vincent Trussart wrote:
>
> System properties != environment variables...
Blurgle... oh well, I guess environment variables are too nonportable
or something. Well, time to put in a real syntax for command-line
switches for the thing- -DBLAH=GRALP is not something I want to type all
th
=bar
> bash$ java myapp
>
> However I can get it with:
>
> bash$ java -Dfoo=bar myapp
>
> What am I doing wrong here?
>
> --
nothing!
System properties != environment variables...
If you want to have access to an environment variable from with a
application, invoke j
Paul Revis wrote:
>no soap. Since System.getenv() is deprecated, I used
>System.getProperty(). I couldn't get it to fetch my variable with what
I
>thought was the correct way:
Check out the documentation for java.util.Properties. Basically,
Properties have no relationship
So I tried to access an environment variable for the first time today;
no soap. Since System.getenv() is deprecated, I used
System.getProperty(). I couldn't get it to fetch my variable with what I
thought was the correct way:
bash$ export foo=bar
bash$ java myapp
However I can get it with:
bash
20 matches
Mail list logo
