I'm finding a bunch of very broken behavior in the 1.2 cvs version: --Package level classes in the same file as a public class break xjavadoc parsing (I wrote a sample to break the build to demonstrate this, but no one has looked into it, except to remove the sample)
--Classes are not always imported in generated code, even when imported as a fully qualified class name in the source file. (found with apparently random classes with the jdo templates and jmx templates). I've discovered both these problems when I update a projects copy of xdoclet to a cvs version. In both cases i've had to also add commons-collection to the classpath. In both cases previously working code generation now fails. I find that I suspect that commons-collection is the cause of these problems. I'd really appreciate someone who is familiar with xjavadoc and the code that finds a fully qualified class name looking into these problems, or at least guessing where the problem might be. Thanks david jencks ------------------------------------------------------- This sf.net email is sponsored by: To learn the basics of securing your web site with SSL, click here to get a FREE TRIAL of a Thawte Server Certificate: http://www.gothawte.com/rd524.html _______________________________________________ Xdoclet-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
