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.
The logic in your post is impeccable though; I'll be darned if I know why
it doesn't work. But then, I know there are many mysteries my poor
intellect will never penetrate, and I'm content for now to chalk this up as
one of them. If anybody in Xalan-land solves this, I'd be interested to
know what's up; but for now I think I'm about done. :)
Cheers,
Neil
Neil Graham
XML Parser Development
IBM Toronto Lab
Phone: 905-413-3519, T/L 969-3519
E-mail: [EMAIL PROTECTED]
|---------+---------------------------->
| | Edwin Goei |
| | <[EMAIL PROTECTED]>|
| | |
| | 10/10/2002 02:33 |
| | AM |
| | |
|---------+---------------------------->
>---------------------------------------------------------------------------------------------------------------------------------------------|
|
|
| To: [EMAIL PROTECTED]
|
| cc: Neil Graham/Toronto/IBM@IBMCA, Gopal Sharma <[EMAIL PROTECTED]>
|
| Subject: Re: can Xalan be compiled under JDK 1.4.x?
|
|
|
|
|
>---------------------------------------------------------------------------------------------------------------------------------------------|
Edwin Goei wrote:
> Sorry, for not thinking and sending out mail too early, please disregard
> the ugly hack idea. I believe the solution would be to use a command
> like the following (psuedocode):
>
> % javac -sourcepath src -d build/classes src/**/*.java
>
> That is, list all source files on the command line. This will force
> javac to compile *all* source files. Ant makes this easy. I haven't
> tried it yet though, since it's getting late and I have to leave the
> office. Let me know if this does not work.
Well, I just looked at the xalan (classic) build.xml file and it
essentially does this. The "compile" target has three separate javac
compiles, but it also prepends the "destdir" to the normal bootclasspath
so it is successful. Since it is split into three batches, the ordering
of each javac batch is important. I tested this with JDK 1.4.0.
It would be simpler to use a single batch, but the comment says this was
done as a workaround for a JDK 1.1.8 bug, which may no longer be
important to support.
-Edwin
