I've confirmed that compiling all the java files for Xalan in one batch
works correctly with Sun JDK 1.4.0. Actually the files in the first batch
have dependencies on the files in the second batch. I think that is why the
Xalan classes in rt.jar are referenced. The reason for the batch separation
is to resolve a JDK 1.1.8 bug. I think JDK 1.1.8 is no longer supported as
a compile platform. So it makes sense to change the build scripts so that
Xalan can be compiled with JDK 1.4.
Morris Kwan
XSLT Development
IBM Toronto Lab
Tel: (905)413-3729
Email: [EMAIL PROTECTED]
Edwin Goei
<[EMAIL PROTECTED]> To: Neil Graham/Toronto/IBM@IBMCA
cc: [EMAIL PROTECTED]
10/10/2002 11:20 Subject: Re: can Xalan be compiled
under JDK 1.4.x?
PM
Please respond to
xalan-dev
[EMAIL PROTECTED] wrote:
> Hi Edwin,
>
> This worked for me if I didn't do a build clean first; if I do
>
> build.bat clean compile
>
> under
>
> java version "1.4.0_01"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0_01-b03)
> Java HotSpot(TM) Client VM (build 1.4.0_01-b03, mixed mode)
>
> then it still blows up.
So you are saying that doing a "clean" first causes it to fail? This is
contrary to what I see. I am using JDK 1.4.0 on unix (Solaris) with my
own version of Ant 1.4.1. In all the times, I've tried, the "compile"
always succeeds whether I do a "clean" or not.
My guess is that any currently available version of the JDK from 1.4.0
to 1.4.1 would behave the same since I don't think much code has changed
in the version of Xalan that is in rt.jar.
Since Xalan is compiling in three batches, perhaps there are some
compile dependencies between the three batches. You could try executing
a single javac batch. I believe, javac will order the dependencies
correctly and compile all files, if you list all java files on the
command line.
-Edwin
