cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Brian May <>
Subject Re: Classpath-based optional compilation (Re: New TagLib, votes please)
Date Tue, 31 Oct 2000 08:22:21 GMT
>>>>> "Jeff" == Jeff Turner <> writes:

    Jeff>  "It was a design error in JDK 1.0 that programmers had to
    Jeff> set the CLASSPATH environment variable. This should have
    Jeff> been set in a property file" --

I think the problem with CLASSPATH is:

a) it contains information specific to each computer. Where is Java
installed? What version is installed? Or, perhaps several different
versions of Java are installed on the one computer.  In this case,
which one should be used? Same Java environments set the CLASSPATH for
this case automatically, however, not all do.

b) it contains information specific to each project.

So, the user typically has to manually setup the CLASSPATH for each
project, with the system specific stuff. I don't think a properties
file will help this...
Brian May <>

View raw message