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 9199] - class compiles with javac but gives class not found errors in javadoc, with same classpath
Date Tue, 11 Mar 2003 06:41:32 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=9199>.
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=9199

class compiles with javac but gives class not found errors in javadoc, with same classpath

stevel@apache.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |WONTFIX



------- Additional Comments From stevel@apache.org  2003-03-11 06:41 -------
I agree, they are inconsistent. But this a quirk of history. <javac> came first.
If we change it now, we break everything that depends on it. <javadoc> is part
of the more strict model used in later systems. failonerror inconsistency is a
similar problem...

Mime
View raw message