DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26570>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26570 duplicate instances of interface com.sun.javadoc.RootDoc loaded ------- Additional Comments From [EMAIL PROTECTED] 2004-02-09 20:01 ------- The point about IDEs is interesting. I've often wondered why you folks still fork a process for javadoc even though there is a programmatic interface, but since javadoc uses the default class loader you would probably have the same problem we are facing. If you wanted to call programmatically, you would depend on the IDE having loaded tools.jar in the default system context. If an IDE provides for setting what gets loaded into the default system context when calling another tool, then your programmatic javadoc call could work, and so could our build, except for the fact that our compile time linkage is not the same as our runtime linkage. I still think that a single .jar file that is available for resolution at compile time, and part of the main system context at run time, would make life much better for project-specific custom tasks. Why not provide an ant-kernel.jar with just the base Ant definitions in it (like Task, Project etc) plus a launcher for the rest? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
