On Fri, 04 May 2007, Steve Loughran <[EMAIL PROTECTED]> wrote: > 1. add a -offline argument to say "we are offline". this will set a > property, (and.build.offline) and the <offline> test will work.
Do I sense oata.utils.NetworkUtils? Might contain some Proxy configuration (and if possible detection) code as well. > 2. when we encounter an element (or even an attr) in an unknown > antlib xmlns, and we want to map that to a projectcomponent, we hand > off resolution to an antlib resolver. We would have one built in > (the failing resolver), would default to the ivy one if it was > present, and provide some way to let people switch to a different > one. OK. > 3. an antlib resolver would do the mapping from antlib package to > artifacts (problem one), actually a pretty big problem. > then download the metadata for that artifact, pull it down and all > its artifacts > > 4. we would then <typedef> the lib with the classpath that is set up > by the resolver sounds right. > we'd need a metadata tree mapping antlibs to well known packages, > but that is not too hard. JSON, perhaps. Not sure. Who'd maintain it? Maintaining it for our own Antlibs is easy, but we wouldn't want the mechanism to only apply for them. And I'd be scared of the security implications of a Wiki driven list or something even close to that. Stefan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
