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 19280] New: - add the ability to echo the <classpath>
Date Thu, 24 Apr 2003 18:11:40 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=19280>.
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=19280

add the ability to echo the <classpath>

           Summary: add the ability to echo the <classpath>
           Product: Ant
           Version: 1.5
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Enhancement
          Priority: Other
         Component: Core tasks
        AssignedTo: dev@ant.apache.org
        ReportedBy: s_p_a_m_bin@hotmail.com


I may be missing something, as I am not an ant guru -- but if there isn't a way
to echo the classpath (the stuff you gather up in your <classpath> element
inside your <javac> task) when doing a compile, then there should be.  And I
couldn't figure out how to do this, so I'll assume that you can't.  

Now I know that you can set up your classpath in a property, and then echo out
that property, but if you have to do things that way just to be able to know for
sure what your classpath really is, then the value of the <classpath> element is
greatly reduced.  

As far as why this should be added, it is widely known that a great number of
compilation troubles involve an incorrectly set classpath.  So it is of obvious
basic utility to everyone to be able to see what classpath their compiler
actually ran against.  They say design for the common case, and this is it!

For example, maybe someone misused the syntax of a <pathelement> in some way and
they are assuming that a jar has been added to the classpath that ant couldn't
find.  It would immediately clue them in that something was wrong with how they
used that <pathelement> if they looked at what their actual classpath was and
saw that the class they thought they included wasn't there.

There are at least a million and one other situations in which this would be
helpful.

Mime
View raw message