ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yannick Menager" <>
Subject RE: Question re: jaxp.jar and parser.jar
Date Tue, 11 Jul 2000 09:07:05 GMT

Yup.. definitly.... Java is the best and greatest language I've ever used, but deployment
and runtime just plain suck.... What it needs is an application/library registry ... I've
started writing one, hopefully it should be finished sometime this year ;) on 10/07/2000 13:47:16

Please respond to

Subject:  RE: Question re: jaxp.jar and parser.jar


I am sorely disappointed with the manner in which "optional packages",
"standard extensions", or just someone else's class library is added to my
Java installation.

Constantly futzing with extremely long classpaths is just gross. Every time
I go to run a project that uses "external" JARs, I scream because I have to
set up classpaths and such. WHY can't the JVM ALWAYS know the classpath to
the system classes (java.*, the standard classes?) I don't understand why
settiing -classpath should make the stupid JVM forget where to find the
important classes. It just plain sucks.

The standard extension mechanism seems like it could ease some headaches,
but like others have noted, having to deal with the JDK installation versus
the JRE, which both have different directory trees, is silly. Why doesn't
the standard JDK installation just stick the JRE binaries in the same place?

Argh. This is one thing that really sucks about Java: it's too
difficult/complicated to load new classes.


Jimmy Sieben

Ericsson Texas R&D

-----Original Message-----
From: Peter Donald []
Sent: Saturday, July 08, 2000 6:30 PM
Subject: Re: Question re: jaxp.jar and parser.jar

At 06:24  8/7/00 -0500, you wrote:
>Maybe I'm missing something obvious, but the installation instructions
>for jaxp1.0.1 state to copy the jaxp.jar and parser.jar to the jre/lib/ext
>directory. Then there is no need include jaxp.jar and parser.jar in
>the classpath because java will find them.

Nooooooooooooooooooooooooooooooooooo !!!!!!!!!!!!! Runaway ! Runaway !

All my experiences using the extension thing as a developer have ended in
pain and suffering. Often I leave things in there which cause bugs down the
road or I install a security manager and they get uneccesarily restricted
etc. So unless it is for an end user I would strongly strongly suggest not
to use extension mechanism if at all possible.

>Is that only for specific situations? I've done that, and still find
>that I have to explictly have jaxp.jar and parser.jar in my classpath
>in order for ant to work correctly...

Not sure is it only with compiling that things break or is it general
running ? Some compilers (ie jikes) need to have it explicitly set
regardless. Other than that I am not sure :<



| "Nearly all men can stand adversity, but if you want |
| to test a man's character, give him power."          |
|       -Abraham Lincoln                               |

View raw message