Hi Lukas, Thanks for sharing your progress. Sorry, I haven't done anything further! :-( Haven't had time for more troubleshooting as I spent a lot of time trying to get multiproject working...I still haven't resolved problems with JDepend either :-((
Basically, I have disabled the report running until I get JDK1.5 setup and running for the CI machine. -----Original Message----- From: Lukas Theussl [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 17, 2005 12:56 PM To: Maven Users List Subject: Re: Maven Validator (maven-xhtml-plugin): Could not start validation: null not found Still trying to get this to work on 1.4...:) Jeff Jensen wrote: > I found using 1.5 eliminates the problem (did you see my follow-up post?). > I have not pursued making 1.4 work though. Java 5 includes xerces while 1.4 doesn't. So I figured I'd just have to include xerces somewhere explicitly to make it work on 1.4. > > I think all it will take for 1.4 (famous last words :-) is setting > org.xml.sax.driver, but again I have not done so. First, it works when running the plugin with the option -Dorg.xml.sax.driver=org.apache.crimson.parser.XMLReaderImpl (crimson is included in 1.4). However, the reports show the same strange error message as above (External parameter entity "%[dtd];" has characters after markup.) for every page. But then, using the option -Dorg.xml.sax.driver=org.apache.xerces.parsers.SAXParser always results in a ClassNotFoundException. I tried including xerces in my project dependencies (added to the root classloader) and in the plugin dependencies, with no success. So the question is: how can I make maven find xerces and include it in its classpath? I saw the note on xerces on the Compatibility page, but it doesn't say anything about what to do about it. > > Thanks for your insight. If you find the solution, please share! :-D > One solution I can offer is to put a xerces jar into $JAVA_HOME/jre/lib/endorsed (you still need to specify the command line option though). However, I would be grateful if somebody could tell me how to get this to work on the plugin level. Thanks, Lukas --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
