[PATCH][GUMP] xml-xalan2-smoketest-experimental-tools project added

[Sh...@lotus.com]

OK, how about this.
xml-xalan/test/qetest.xml builds the custom Ant task (and the independent
qetest framework, to boot, which I wanted to do sometime anyway) with no
dependencies (well, besides Ant)

xml-xalan/test/build.xml uses that custom task (that was presumably built
in the same tree that it's about to build in...) to get it's custom task
defined, and then goes on it's merry way.

Sound good?  Or am I still missing something from cross-product
coordination?  For Xalan purposes, the only useful output of qetest.xml is
the XSLTestAntTask.class file in the proper place; the build.xml file will
ask to recompile the qetest files anyway, although obviously won't need to
since they've already been compiled.

Yes, I now have a small amount of duplicate code in build.xml/qetest.xml,
but that's my maintenance question.  And maybe someday I'll build some
qetest tests for Xerces and get qetest put into xml-commons... (sorta
vaguely like junit, but for quality engineers, not just developers)

- Shane

cvs -q diff xml-xalan.xml (in directory E:
\builds\jakarta-alexandria\proposal\gump\project\)
Index: xml-xalan.xml
===================================================================
RCS file:
/home/cvspublic/jakarta-alexandria/proposal/gump/project/xml-xalan.xml,v
retrieving revision 1.14
diff -r1.14 xml-xalan.xml
74a75,85
>   <project name="xml-xalan2-smoketest-tools">
>     <description>
>       Xalan's independent 'qetest' testing framework
>     </description>
>
>     <ant basedir="test" buildfile="qetest.xml" target="jar"/>
>
>     <depend project="jakarta-ant"/>
>     <work nested="test/java/build"/>
>   </project>
>
84a96
>     <depend project="xml-xalan2-smoketest-tools"/>






---------------------------------------------------------------------
To unsubscribe, e-mail: alexandria-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: alexandria-dev-help@jakarta.apache.org