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] New: - class compiles with javac but gives class not found errors in javadoc, with same classpath
Date Fri, 17 May 2002 10:13:15 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

           Summary: class compiles with javac but gives class not found
                    errors in javadoc, with same classpath
           Product: Ant
           Version: 1.4.1
          Platform: PC
               URL: http://www.aaa.net.au/campbell/junk.jar
        OS/Version: Windows NT/2K
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Core tasks
        AssignedTo: ant-dev@jakarta.apache.org
        ReportedBy: david@pastornet.net.au


Ant's <javac> behaviour seems to be that it allows classes to use java libraries
that are not specified in the classpath in the build.xml, but are part of the
ant distribution.

Ant's <javadoc> behaviour seems to be the reverse.

Thus, if you have a class that uses something from crimson.jar, which is
included in the ant distro, then it will compile without being specified on the
classpath, but javadoc will yield class not found.

This seems wrong.  I think they should be consistent.

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


Mime
View raw message