ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 26570] - duplicate instances of interface com.sun.javadoc.RootDoc loaded
Date Tue, 03 Feb 2004 19:55:53 GMT
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 eric@sandservices.com  2004-02-03 19:55 -------
That was a good idea, and it fixes RootDoc, but my own linkage is still
broken at runtime.  What I end up with is a Class instance being found for
RootDoc where getClassLoader() returns null.  There's still not enough
loaded in at startup for my custom task to have the view of the world it
had when it was compiled. 

Here's what is needed in the default ClassLoader:
    FooStuff.jar (necessary for callbacks into custom task info)
    tools.jar (so my custom task can get to com.sun.javadoc.RootDoc)
    ant.jar (so my custom tasks can extend org.apache.tools.ant.Task)

The first two should be specified in ANT_OPTS, but FooStuff.jar won't load
without Task, Project and other base Ant classes.  In trying to force this
by specifying all 3 in ANT_OPTS, I've kind of hit a wall: ant.jar won't
load because it needs AntMain, but when I add ant-launcher.jar in it fails
on an NPE in getResourceSource.  Clearly at this point I am swimming
against the tide of how Ant 1.6.0 wants to launch.  If there were an
independent ant-kernel.jar file with just Task, Project and other base Ant
Class declarations, then this approach might work. 

>From what I can tell, if the base class declarations and the Launcher were
jarred together, that could provide an "Ant kernel" capable of boot linkage
and easy generalized extension.  I think something like that might solve my
problem, and provide an easier migration path from 1.5.4 where ant.jar was
fully self-contained.  It might also help segmentation of custom tasks,
since they would compile against ant-kernel.jar and only require that at
runtime, which allows for more flexibility in what gets launched.  Any
chance of something like this in the works? 

Any other thoughts/ideas/suggestions?

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org


Mime
View raw message