Re: Build instructions out of date

I assume the tests are private.  I didn't see any tests by those names  
in the CVS and the current CVS builds without complaint.

I've committed a change to test-to-java that will fix the cast to  
HTMLDocument issues on load.  The other issues are due to not  
specifying the interface attribute when there is an ambiguity.  Running  
dom2-html-validate-tests should have identified the tests are invalid.   
I also try to Sun's Multi-schema Validator for to schema validate.

Are there any feelings about inquiring about being included in Gump's  
(http://jakarta.apache.org/gump/) massive automated build?

On Wednesday, February 12, 2003, at 10:27 AM, Philippe Le Hegaret wrote:

>
> Thanks for the update Curt. I updated the page following your
> instructions:
> http://www.w3.org/DOM/Test/Documents/DOMTSBuild.html
>
> I'm in the process of testing the build process. I got the following
> error for the moment:
>
> dom2-html-javac:
>     [javac] Compiling 614 source files to  
> /home/plehegar/dev/2001/DOM-Test-Suite/build/java
>     [javac]  
> /home/plehegar/dev/2001/DOM-Test-Suite/build/java/org/w3c/domts/ 
> level2/html/createHTMLDocument01.java:69: incompatible types
>     [javac] found   : org.w3c.dom.Document
>     [javac] required: org.w3c.dom.html2.HTMLDocument
>     [javac]       doc = load("anchor");
>     [javac]                 ^
>     [javac]  
> /home/plehegar/dev/2001/DOM-Test-Suite/build/java/org/w3c/domts/ 
> level2/html/createHTMLDocument02.java:79: incompatible types
>     [javac] found   : org.w3c.dom.Document
>     [javac] required: org.w3c.dom.html2.HTMLDocument
>     [javac]       doc = load("anchor");
>     [javac]                 ^
>     [javac]  
> /home/plehegar/dev/2001/DOM-Test-Suite/build/java/org/w3c/domts/ 
> level2/html/createHTMLDocument02.java:85: cannot resolve symbol
>     [javac] symbol  : class TreeWalker
>     [javac] location: class  
> org.w3c.domts.level2.html.createHTMLDocument02
>     [javac]       headEl = (HTMLElement) ((TreeWalker) /*Node  
> */htmlEl).firstChild();
>     [javac]                                ^
>     [javac]  
> /home/plehegar/dev/2001/DOM-Test-Suite/build/java/org/w3c/domts/ 
> level2/html/createHTMLDocument02.java:87: cannot resolve symbol
>     [javac] symbol  : class TreeWalker
>     [javac] location: class  
> org.w3c.domts.level2.html.createHTMLDocument02
>     [javac]       bodyEl = (HTMLElement) ((TreeWalker) /*  
> */nodeList).nextSibling();
>     [javac]                                ^
>     [javac]  
> /home/plehegar/dev/2001/DOM-Test-Suite/build/java/org/w3c/domts/ 
> level2/html/createHTMLDocument02.java:87: cannot resolve symbol
>     [javac] symbol  : variable nodeList
>     [javac] location: class  
> org.w3c.domts.level2.html.createHTMLDocument02
>     [javac]       bodyEl = (HTMLElement) ((TreeWalker) /*  
> */nodeList).nextSibling();
>     [javac]                                                 ^
>     [javac]  
> /home/plehegar/dev/2001/DOM-Test-Suite/build/java/org/w3c/domts/ 
> level2/html/createHTMLDocument02.java:89: cannot resolve symbol
>     [javac] symbol  : class TreeWalker
>     [javac] location: class  
> org.w3c.domts.level2.html.createHTMLDocument02
>     [javac]       titleEl = (HTMLElement) ((TreeWalker) /*Node  
> */headEl).firstChild();
>     [javac]                                 ^
>     [javac]  
> /home/plehegar/dev/2001/DOM-Test-Suite/build/java/org/w3c/domts/ 
> level2/html/createHTMLDocument02.java:92: cannot resolve symbol
>     [javac] symbol  : class TreeWalker
>     [javac] location: class  
> org.w3c.domts.level2.html.createHTMLDocument02
>     [javac]       content = (Text) ((TreeWalker) /*Node  
> */headEl).firstChild();
>     [javac]                          ^
>     [javac] 7 errors
>
> BUILD FAILED
> file:/home/plehegar/dev/2001/DOM-Test-Suite/build.xml:1305: Compile  
> failed; see the compiler error output for details.
>
>
> I'll keep testing the build process and trying to fix it as well. I'd
> like to add the tests submitted by IBM asap.
> I also need to check with Dimitris regarding the JSUnit framework. We
> did discuss the framework at the face-to-face meeting and we concluded
> that the framework from Bob is probably the best to follow. Not sure  
> how
> this fits with JSUnit 1.3.3 though.
>
> Philippe
>
> On Wed, 2003-02-12 at 00:57, Curt Arnold wrote:
>> From: http://www.w3.org/DOM/Test/Documents/DOMTSBuild.html
>>
>> Software needed prior to build
>>
>> You will need the following software to build the DOM TS (the Java and
>> ECMA Script code, the DOM TS Markup Language in W3C Schema and DTD  
>> form.
>>
>>      * Ant 1.4 as well as the ant-optional.jar
>>      * Xalan
>>      * SED , links to many downloadable SED binaries
>>      * Patch
>>
>> Download the Ant 1.4 and Xalan-J2.1 binaries. In the Ant directory,
>> remove crimson.jar and jaxp.jar from the lib directory and put
>> xerces.jar and xalan.jar in their place. This combination works well;  
>> we
>> have noted that other processors get broken by the transforms we use.
>>
>> Make sure you have included ant/bin, sed and patch on your path and  
>> set
>> JAVA_HOME.
>>
>> Make DOM-Test-Suite the current directory (or, if you just want to  
>> test
>> the build, copy all files from the DOM-Test-Suite directory to a
>> location of your choosing) and do:
>>
>> ant usage
>>
>> to see what options you have to build the DOM TS.
>>
>>
>> ---------
>>
>> Sed and Patch are no longer needed (unless you are generating SVG
>> DOMTSML which is experimental)
>>
>> Ant 1.5.1 is the current version of Ant.  The build requires at least
>> Ant 1.5, 1.4 will no longer work.
>>
>> It is not necessary to remove any jars.  The only modification to Ant  
>> is
>> placing saxon.jar from Saxon 6.5.2 (http://saxon.sourceforge.net) into
>> the /jakarta-ant-1.5.1/lib directory.
>>
>> I've been running a xalan.jar built from the Xalan CVS without  
>> incident,
>> however Xalan-J 2.4.1 seemed to be churning on some of the transforms  
>> in
>> dom1-core-gen-java just a few seconds ago and I had to kill it.  I
>> believe that all the issues with Xalan have been fixed, just need to
>> have another release before we could recommend it for building the  
>> test
>> suite.
>>
>> If you get a out of memory error, you can increase heap size on most  
>> Sun
>> VM's by setting:
>>
>> SET ANT_OPTS=-Xmx512M
>>
>> jsunit.zip from http://www.jsunit.net will need to be places in
>> 2001/DOM-Test-Suite/lib to build to the jsunit tests.
>>
>> I believe that any Java VM 1.1 or later will work.  I typically use  
>> JDK
>> 1.3 on Windows XP.  I've also built the suite on SuSE Linux 8.0 and  
>> Mac
>> OS 10.2.3.
>>
>