While messing around with QDox, I noticed a few parse errors that I only explain by the fact the files use MACintosh line endings.
Here are some samples:
On these files http://cvs.sourceforge.net/viewcvs.py/xdoclet-plugins/xdoclet-plugins/plugin-beaninfo/src/test/java/org/xdoclet/plugin/beaninfo/BeanInfoPluginTestCase.java it goes "syntax error @[44,1]"
http://cvs.sourceforge.net/viewcvs.py/xdoclet-plugins/xdoclet-plugins/plugin-jmx/src/test/java/org/xdoclet/plugin/jmx/MBeanPluginTestCase.java it goes "syntax error @[56,1]"
http://cvs.sourceforge.net/viewcvs.py/xdoclet-plugins/xdoclet-plugins/plugin-jmx/src/test/java/org/xdoclet/plugin/jmx/MLetPluginTestCase.java it goes "syntax error @[57,1]"
It so happens that in all theses cases, the error lines are the last line from the file and are empty. My only guess is that the parser goes nuts because of the mac line endings, but still, after converting the files to DOS format, I got the same errors. (different line numbers because i also did code layout, since the mac format introduced many blank lines)
As you might have guessed, I got these errors while trying to put together an xdoclet plugin. I had to hack xdoclet's sources to see what files were causing problems, because as far as I could tell, qdox's only entry point is a java.io.Reader, right? If not, I guess it would be great to have the error message tell what file was wrong. [To xdoclet'ers: can we do something about this in xdoclet? So that an unparseable source is at least identified by it's filename?]
Thanks for any info or tip,
Cheers,
greg
------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ xdoclet-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
