> I don't see the need for /etc/java-core-classes. Every VM should be
> able to find its core classes without it. This implies that there
> should be no need to put core classes into CLASSPATH.
1. Some (many?) compilers don't provide their own core classes, and need
the location of core cla
> I don't see the need for /etc/java-core-classes. Every VM should be
> able to find its core classes without it. This implies that there
> should be no need to put core classes into CLASSPATH.
1. Some (many?) compilers don't provide their own core classes, and need
the location of core cl
> "Ean" == Ean R Schuessler <[EMAIL PROTECTED]> writes:
Ean> Yeah, this is kind of good. I was thinking about a system
Ean> where each Java aware package puts a file in an /etc dir,
Ean> with init.d looking priorities.
Ean> So you might have:
Ean> /etc/java/classpaths/
> "Ean" == Ean R Schuessler <[EMAIL PROTECTED]> writes:
Ean> Yeah, this is kind of good. I was thinking about a system
Ean> where each Java aware package puts a file in an /etc dir,
Ean> with init.d looking priorities.
Ean> So you might have:
Ean> /etc/java/classpaths/
> > >From Edouard G. Parmelan <[EMAIL PROTECTED]>, one of the Kaffe upstream
> > >developers,
> > a proposal to the Java policy:
> >
> > Each java-virtual-machine comes with a /etc/java-core-classes (using
> > alternatives to manage it). This file contains the list of jars and
> > directories w
Yeah, this is kind of good. I was thinking about a system where each Java
aware package puts a file in an /etc dir, with init.d looking priorities.
So you might have:
/etc/java/classpaths/
00_Kaffe.txt
10_JServ.txt
.
.
.
All of these would get sourced to form a composite CLAS
> > >From Edouard G. Parmelan <[EMAIL PROTECTED]>, one of the Kaffe upstream developers,
> > a proposal to the Java policy:
> >
> > Each java-virtual-machine comes with a /etc/java-core-classes (using
> > alternatives to manage it). This file contains the list of jars and
> > directories with c
Yeah, this is kind of good. I was thinking about a system where each Java
aware package puts a file in an /etc dir, with init.d looking priorities.
So you might have:
/etc/java/classpaths/
00_Kaffe.txt
10_JServ.txt
.
.
.
All of these would get sourced to form a composite CLA
Stephane Bortzmeyer wrote:
>
> >From Edouard G. Parmelan <[EMAIL PROTECTED]>, one of the Kaffe upstream
> >developers,
> a proposal to the Java policy:
>
> Each java-virtual-machine comes with a /etc/java-core-classes (using
> alternatives to manage it). This file contains the list of jars and
>
Stephane Bortzmeyer wrote:
>
> >From Edouard G. Parmelan <[EMAIL PROTECTED]>, one of the Kaffe upstream developers,
> a proposal to the Java policy:
>
> Each java-virtual-machine comes with a /etc/java-core-classes (using
> alternatives to manage it). This file contains the list of jars and
> di
>From Edouard G. Parmelan <[EMAIL PROTECTED]>, one of the Kaffe upstream
>developers,
a proposal to the Java policy:
Each java-virtual-machine comes with a /etc/java-core-classes (using
alternatives to manage it). This file contains the list of jars and
directories with core classes.
For Kaf
>From Edouard G. Parmelan <[EMAIL PROTECTED]>, one of the Kaffe upstream developers,
a proposal to the Java policy:
Each java-virtual-machine comes with a /etc/java-core-classes (using
alternatives to manage it). This file contains the list of jars and
directories with core classes.
For Kaff
12 matches
Mail list logo
