.---- you Gary L Peskin <[EMAIL PROTECTED]> wrote ----
> I have a quick question as to how the various developers do his or her
> compiles. I know that we're supposed to make it so that XalanJ will run
> under JDK 1.1.x.
>
> How do you enforce this?
Excellent question. Either someone still on JDK 1.1.8 occasionally
complains, or usually I become version police, since I make sure to switch
between JVM's freuently and usually have an _003 or _004 version on one of
my Windows boxes. It's nothing organized. 8-)
> I'm asking because up until now I've been doing it by using the Sun JDK
>1.1.8 javac compiler. I'm using 1.1.8_007 which is one less than the
>latest version. However, I was unable to compile the latest CVS for two
>reasons: First, the classes XString, XNumber, XBoolean, and XNull won't
>compile because of a cyclic class definition error. I think this is
>because of the static methods in XObject which use those classes even
>though those classes extend XObject and need it to be compiled first. I
>know that this worked before with the single static create method that
>took one argument but it doesn't seem to work now.
The answer here is either add an extra constructor or try splitting the
javac steps up into more separate compiles. That's why the compile target
has so many separate <javac ... > tasks, for JDK 1.1.8. If this is truly a
small circular dep. that 1.1.8 can't figure out, we may be stuck though.
>Also, the latest change to NamespaceSupport2 which invokes a method on
>an anonymous class also seems to confuse the JDK 1.1.8 compiler.
This was Joe; he was asking me about this. This could be a more serious
problem.
>My solution was to use the Java 1.3 compiler with the "-target"
>argument. However, I noticed that we haven't used that in our
>build.xml. So, since I already use an Ant BuildListener to suppress
>stuff in the CVS directories I just added a call to setTarget in there.
Rowf? (picture a dog with one ear cocked looking quizzical) I guess I
haven't played with 1.3 enough yet. Why do we explicitly need this? Also,
let's make sure that our Ant build file is still compatible with 1.1.8 and
at least 1.2. Hey, could you send out how you setup your BuildListener so
we can play with it? And doesn't Ant already ignore the CVS directories?
(sorry, I'm starting to blather since it's too hot at home...)
>Shane, Myriam, Joe, Scott, etc. --- What do you do to make sure the
>stuff compiles/runs in 1.1.8?
>
>Gary
Ah - a good point. We should separate the compile versus runtime
compatibility requirements for the Xalan community. I think the xsltc folk
will vote along with me that we should keep everything running in 1.1.8.
We could start to discuss only requiring JDK 1.2 to compile sometime soon
if people wanted to, although I'll want to see plenty of time before a
final decision is made so everyone has a chance to comment. Yes, Virginia,
there *are* people who really can't upgrade their applications to JDK 1.2
yet...
- Shane
