I actually just figured out that it was a discrepancy in the version of the VSS pull I had. I was working on a local copy of our VSS for testing purposes, and they didn't tell me about a few changes that were in progress during my initial pull. From what I can tell, the class involved (and subsequent similar errors) were ones that were never even compiled to class files.
Thanks for the attention though! Scott -----Original Message----- From: Arnaud HERITIER [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 08, 2005 2:44 PM To: 'Maven Users List' Subject: RE: javadoc processing problem Can you send us the trace generated with : maven -Dmaven.javadoc.debug=true -e javadoc Arnaud > -----Message d'origine----- > De : Scott Richardson [mailto:[EMAIL PROTECTED] > Envoy� : mercredi 8 juin 2005 18:48 > � : [email protected] > Objet : javadoc processing problem > > Has anyone ever seen something like this? > > [javadoc] Copying file C:\Documents and > Settings\<username>\.maven\cache\ma > ven-javadoc-plugin-1.7\plugin-resources\stylesheet.css to > file C:\<path > to>\stylesheet.css... > [javadoc] Building index for all the packages and classes... > [javadoc] Building index for all classes... > [javadoc] Generating C:\<path to>\help-doc.html... > [javadoc] 34 warnings > [delete] Deleting directory > C:\VSS\CCwrk\checkout\DIB\target\javadoc\src > > [echo] Generating the Source Xref... > maven-jxr-plugin:report: > [echo] > Scanning C:\<path to> > Unable to process C:\<path to>\ADEScreener.ja va => C:\<path > to>\ADEScreener.html > > BUILD FAILED > File...... C:\Documents and > Settings\<username>\.maven\cache\maven-jxr-plugin-1.4.2\plugin.jelly > Element... jxr:jxr > Line...... 105 > Column.... 31 > java.lang.NullPointerException > Total time: 5 minutes 57 seconds > Finished at: Wed Jun 08 11:21:47 EST 2005 > > It seems that the javadocs up till that point are being > generated correctly (I found them in the docs dir). The > program compiles correctly as well. > Interesting to note is the project requires some dependencies > put in the C:\Program Files\Apache Software Foundation\Maven > 1.0.2\lib\endorsed Directory, which allows it to compile. > However, when the javadocs do their thing, they don't seem to > use it, as they are throwing the same errors I was getting > before putting the dependencies in when trying a general > compile (which are interpreted as warnings by javadoc, which > is ok, as they are part of a different package that I'm not > wanting to create docs for). > > Also, this file that's throwing the errors isn't involved in > any of the javadoc warnings. > > Any suggestions? > > Thanks, > Scott > > --------------------------------------------------------------------- > 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
