From: [EMAIL PROTECTED]
Are you sure that you don't have any system property that points to
another
parser?
I surely havent set anything.
Are you sure that you don't have other parsers in the /jre/lib/ext
directory?
Absolutely .. given the number of things i work on simultaneously, i
arg value=-uWARN/
to read
arg value=-uINFO/
-uINFO did not give anything extra, but a combination of -uDEBUG and ant in
verbose mode gave the following (huge) output .. but nothing that caught my
eye :(
owdocs:
Forking C:\jdk1.3\jre\bin\java.exe -classpath
]
To: Nicola Ken Barozzi [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; Rainer Klute [EMAIL PROTECTED]
Sent: Wednesday, April 10, 2002 6:28 PM
Subject: Re: Build: Crimson missing
Ok guys, it should be fixed.
Unfortunately it isn't fixed. Since I couldn't do a CVS update I
tried a CVS checkout
From: [EMAIL PROTECTED]
The solution for 1.3 (which will also work for 1.4) should be to set
className=org.apache.xerces.parsers.SAXParser attribute in the
xmlvalidate
tag within the validate-docs target, which forces xmlvalidate to use that
class
(the default being the crimson class since
Hi Ken,
after a fresh CVS checkout (just to make sure) the build behaves
quite differently but still doesn't work:
...
validate-docs:
BUILD FAILED
/share/mark/work/jakarta-poi/tools/cents/forrest.cent/xbuild.xml:114: Could not start
xml validation: org.apache.crimson.parser.XMLReaderImpl
can you give a java -version and an echo $CLASPATH ? I'm not getting
this error.
Rainer Klute wrote:
Hi Ken,
after a fresh CVS checkout (just to make sure) the build behaves
quite differently but still doesn't work:
...
validate-docs:
BUILD FAILED
