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] New: - duplicate instances of interface com.sun.javadoc.RootDoc loaded
Date Sat, 31 Jan 2004 20:05:21 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

           Summary: duplicate instances of  interface
                    com.sun.javadoc.RootDoc loaded
           Product: Ant
           Version: 1.6.0
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Core
        AssignedTo: dev@ant.apache.org
        ReportedBy: eric@sandservices.com


In 1.6.0, interface com.sun.javadoc.RootDoc is loaded twice.  Finding it via 
Class.forName produces an instance with a different hashCode than what's in 
the parameter signature of a loaded doclet in our doclet path.  Note that we 
are doing this call from within a custom task, NOT from the forked javadoc 
process, so we are talking about loading in the main thread, not for a new 
javadoc VM.

Having two instances of a loaded class is a problem.  It could be alleviated 
if java.lang.Class defined an equals method that tested based on the name, 
rather than the instance, then getMethod could find the appropriate Method in 
either case.  But the official position is that you shouldn't have two 
instances of the same class floating around.

We've exhausted the workarounds we know of, once the duplicates are loaded
there doesn't seem to be much way around this.  If you have any suggestions 
please let me know.

I don't know where to start looking for this in the Ant code.  I'm presuming 
it was forced in at some point?  Version 1.5.4 works fine, so we'll use that 
for now and check subsequent releases as they happen.

thanks,
-ep

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


Mime
View raw message