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 3989] New: - Available tasks test always user classpath
Date Fri, 05 Oct 2001 13:26:58 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=3989>.
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=3989

Available tasks test always user classpath

           Summary: Available tasks test always user classpath
           Product: Ant
           Version: 1.4
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Core tasks
        AssignedTo: ant-dev@jakarta.apache.org
        ReportedBy: cziegeler@apache.org


We recently had the problem with that the
"available" task always searches not only in the 
given classpath for a class but also in the parent
classloader (= jdk user classpath). 
If I specify:
    <available classpathref="classpath" 
               property="naming.present" 
               classname="javax.naming.Context"/>
I assume that the class is only used in the classpath
defined by classpathref. 

Looking at the source I saw that the AntClassLoader
theoretically supports the "isolated" feature
which prevents searching in parent class loaders.
Is it planned to add an optional attribute to
the available task to specify the behaviour of
this search? 


However just patching the Available class to
support setting the isolated flag on the classloader
is not enough as the isolated flag seems not to 
be evaluated correctly. For example the loadClass()
method always calls isParentFirst(), but in insolated
mode the parent should never be queried.

Mime
View raw message