- From: Christopher William Turner <cwturner@cycom.co.uk>
- Date: Thu, 10 Dec 1998 07:37:52 -0500 (EST)
- To: "www-jigsaw@w3.org" <www-jigsaw@w3.org>
- Message-ID: <366FBF9C.5EEE7540@cycom.co.uk>
I found the same compile problems as Butch Landingin. However I was able to successfully compile and run the previous jigsaw 2.0beta2 with JDK1.2beta4 and JSDK2.0 (also JAVA_COMPILER=NONE) Just one compile error in an unused test program (see attached err.rpt). I used my own build system rather than the supplied Makefiles and this rejected many unused source files (see attached rejects.rpt). There are many cyclic dependencies between classes, even cross package cycles. This might cause subtle problems if you do not delete all class files before building. These cycles could be broken by more use of interfaces. (see attached cycles.rpt) The result runs OK for my purposes. Jigsaw is reasonably happy but throws IndexOutOfBounds exceptions in HttpParser.parseInt() on some sites due to failure to keep the ParseState consistent with the byte buffer lengths. Jigadm is happy provided you stretch its windows to aid layout (best with 1024 pixel screen). There is a intermittent bug adding and removing filters to the Proxy properties and I had to manually edit a property file to get it to remember. I may have been making errors with commit/checkpoint/save and tried many combinations. These might be fixed in 2.0b3 but with all the compile errors I haven't tried. -- Chris Turner, http://www.cycom.co.uk/
Attachments
- application/x-unknown-content-type-rpt_auto_file attachment: err.rpt
- application/x-unknown-content-type-rpt_auto_file attachment: rejects.rpt
- application/x-unknown-content-type-rpt_auto_file attachment: cycles.rpt
Received on Thursday, 10 December 1998 08:12:20 UTC