[EMAIL PROTECTED] wrote: >>Bootstraping is not enough. > > And I didn't just bootstrap. I also ran maven site to ensure most of the > goals you mention below functioned correctly. > > And they did. I can email you the text file of the build and run if you > like.
Take it easy, that's not neccessary! I believe it works for you, I just want it to work for me also :) >>[ERROR] Caused by: javax.xml.parsers.FactoryConfigurationError: Provider >>org.apache.xerces.jaxp.SAXParserFactoryImpl not found > > This is xerces not being found. I can't see why from the output and stack > trace. I know that. Please tell me what information can I give you? I'm willing to dig into this problem. >>Looks like JDK 1.4 vs Xerces issue to me. I doublechecked that >>xerces.jar is in $MAVEN_HOME/lib and in $MAVEN_HOME/lib/endorsed, it is >>mentioned in forehead.conf, my $CLASSPATH is blank... > > $CLASSPATH isn't used by Maven. I know that it uses Forehead. Just making sure that I don't have any silly stuff hanging aroud. >>Goals that fail with SAXParser error: checkstyle, dist, javadoc, >>pom:validate > > Of these, I've not personally tested dist and pom:validate. All others > work for me on 1.3.1->1.4.1_01 These also worked for me some time around Beta 7, but not today :-( > The only thing I can think of is you have a bad pull from CVS. I don't think so. cvs up does not give me any suspicious output. I also checked xerces & xmlapis jars integrity and they seem to be fine. OTOH xerces *does* work, it certainsly succeeds in reading some files, but later 'is not found'. Seem like classloader mess to me. Rafal -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
