I just checked and found that compilation under JDK 1.1.8 is already
broken. There are a lot of errors with messages like " Cyclic class
inheritance or scoping". This is exactly the same error the workaround of
separating the build into three batches was supposed to fix. I think this
workaround is just not such a good solution and it is easy to break when
the dependencies between the files are changed.
My understanding is we support JDK 1.1.8 as a runtime platform but not a
compile platform. Is that true? If this is the case, then we can drop any
hack in the build scripts to support JDK 1.1.8. The workaround is not
working at the moment. I think we do not want to hack it again because the
workaround solution is easy to break in the future.
Morris Kwan
XSLT Development
IBM Toronto Lab
Tel: (905)413-3729
Email: [EMAIL PROTECTED]
Claude Warren
<[EMAIL PROTECTED] To: [EMAIL PROTECTED]
g> cc:
Subject: Re: can Xalan be compiled
under JDK 1.4.x?
10/11/2002 10:41
AM
Please respond to
xalan-dev
I thought that Sun and IBM were dropping support for the 1.1.x JDK. If
that is so I would think that it would be ok to drop support for 1.1.x
some time after that support is dropped. (e.g. don't support 1.1.8 six
months after support for 1.1.8 is dropped)
Claude
Joseph Kesselman wrote:
> Last I checked, we still have some users who claim _their_ users can't
> upgrade from 1.1.8. Being able to compile against that version is still
> part of our official spec. I'd love to drop it, but I don't think that's
> on the table yet.
>
> On the other hand, it might not be unreasonable to have a separate ANT
> build target for that case, or (if ANT will let us) to conditionalize the
> build based in the JVM available. If that gets us out of this hole...
>
> ______________________________________
> Joe Kesselman / IBM Research
