> - Most importantly - is there a way to fix the command-line length issue > when spawning javadoc? How do folks handle this constraint?
I run it on win2k/xp and *very long* list of arguments and no problems. I think you need to enhance the size of command line arguments (in win98 you can right click on bat file, properties and change the size). > - How can I get rid of the log4j error messages? You shouldn't have that problem. Are you using xdoclet.jar from xdoclet's distribution? > - When XDoclet does run, how can I get rid of all the javadoc warnings > about > imports not found? I'm assuming by putting those dependencies in the > classpath specified? But for <info> its no important if those classes are > in the classpath, right? If you setup classpath or classpathref param of doclet properly there shouldn't be any warnings. PS: warnings, problems with forking javadoc.exe, etc, all will be gone when we start using xjavadoc. Ara. _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com _______________________________________________ Xdoclet-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
