---- Sam asked ----
> Why check this class in? It is build by the build process, and already
on
> the classpath. In fact, the version built is of a different size - any
> explanation?
1) Um, because otherwise Ant will barf on the build.xml file when I attempt
to do:
<taskdef name="xalantest" classname
="org.apache.qetest.xsl.XSLTestAntTask">
...at least as far as I can tell. What is the solution to a project that
wants to use a custom Ant task that requires an external .class or .jar
file that's *not* checked into Ant (and *not* in Ant's optional.jar,
although I should probably submit this over there someday)? Which class
gets loaded first: Chicken.class or Egg.class? 8-) I explicitly didn't
add this to the classpath in build.bat/.sh since I figured that's even
harder to manage, esp. with external build systems.
2) Re: sizes: well, I just checked in new matching .java and .class files,
although I just realized I was naughty and checked in the file I compiled
under IBM JDK 1.3 (I really should have used JDK 1.1.8 to ensure
compatibility). Perhaps the new changes, or the difference in compilers
explains the size diff?
Or am I missing some build step that I implement in (some sort of
standardized way) that compiles this class before we ever call the normal
build.xml? But that doesn't work either, since XSLTestAntTask actually
depends on (fairly stable interfaces in) org.apache.qetest.*, so I'd have
to compile that whole set too. Where does the bootstrap end? Why am I
asking so many amusing rhetorical questions today?
- Shane
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
