[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
