I found using 1.5 eliminates the problem (did you see my follow-up post?).
I have not pursued making 1.4 work though.

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.

Thanks for your insight.  If you find the solution, please share!   :-D
 

-----Original Message-----
From: Lukas Theussl [mailto:[EMAIL PROTECTED] 
Sent: Monday, July 04, 2005 1:31 PM
To: Maven Users List
Subject: Re: Maven Validator (maven-xhtml-plugin): Could not start
validation: null not found


Just a comment: I am having basically the same problem with maven
1.1-beta-1 (everything works fine with 1.0.2).

However, I noticed something weird: I have a project B that extends project
A.

If I run 'site' in project A, I get the above error (Could not start
validation: null not found), and the build stops.

If I run 'site' in projet B, the build goes through, the xhtml report gets
generated but contains a number of strange error messages for each html page
that I didn't have before (External parameter entity "%[dtd];" 
has characters after markup.) ?

If I run 'multiproject:site' in project A, the build goes through but the
xhtml report page contains just an empty placeholder (' This file is used as
a placeholder until the final xhtml validation can occur.').


I have checked the Compatibility page on the maven web site but I can't
figure out what to do to make the xhtml plugin work again.

Hope somebody can help.
Cheers


PS I am running java 1.4, I didn't try with 1.5.


Jeff Jensen wrote:
> (Is this the correct list for help on this plugin?  Its web page does 
> not have a list listed, it is not listed on sf's "Maven Plugins", but 
> it is hosted on sf, so I am not sure.)
> 
> I am using Maven beta 1.1 and trying to get the Validator "3rd party" 
> plugin working (maven-xhtml-plugin).
> 
> The following problem occurs:
> 
> Could not start validation: null not found at 
> org.apache.maven.xhtml.Validator.initValidator (Validator.java:176)
> 
> Has anyone seen this before?
> 
> The offending lines are:
>         // turn validation on
>         try
>         {
>             this.xmlReader = XMLReaderFactory.createXMLReader();
>             this.xmlReader.setFeature(VALIDATION_FEATURE, true);
>         }
>         catch (SAXNotRecognizedException e)
>         {
>             throw new BuildException("Could not start validation: " + 
> this.xmlReader + " doesn't provide validation");
>         }
>         catch (SAXNotSupportedException e)
>         {
>             throw new BuildException("Could not start validation: " + 
> this.xmlReader + " doesn't provide validation");
>         }
>         catch (SAXException e)
>         {
>             throw new BuildException("Could not start validation: " + 
> this.xmlReader + " not found");
>         }
> 
> 
> So a SAXException was thrown, probably by
"XMLReaderFactory.createXMLReader()".
> 
> From the Javadoc: "This method uses the value of the system property 
> "org.xml.sax.driver" as the full name of a Java class and tries to 
> instantiate that class as a SAX2 XMLReader."
> 
> I wonder if I have to set "org.xml.sax.driver" system property?
> 
> Or is there an extra config step I need to do that I did not see on 
> the plugin web site instructions?
> 
> Regretfully the real exception message is swallowed.  And before I 
> have to get source and modify and build to see it, I am hoping someone 
> has a quick & easy answer to the problem!  :-)


---------------------------------------------------------------------
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]

Reply via email to