In looking back at old bugreps, I reread: http://issues.apache.org/bugzilla/show_bug.cgi?id=4066
Which asks for a nested classpath on <ant> & co. Since these create a subproject, it seems it wouldn't be difficult to setCoreLoader on the Project instance, and all would be well. To test this, I tried <available resource="" />, which, to my surprise, failed, due to the fact that available doesn't consult the coreLoader of its parent Project when checking the availability of a class or resource. Shouldn't available's code defer to something (in ClasspathUtils perhaps) to make this uniform? -Matt __________________________________ Do you Yahoo!? Make Yahoo! your home page http://www.yahoo.com/r/hs --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]