On 16 Jul 2002, Stefan Bodewig wrote: > > However, as I mentioned in one of the many mails, I would also like > > a solution that can be aplied to ant1.5. > > No problem - but that's been your 1.6 itch list, you know ;-)
My mistake - the itches are in ant1.5, I just want 1.6 to solve them :-) But now it seems pretty clear that solving them for 1.5 would be much better - and we can get more feedback for a better solution for 1.6. > > If everyone agrees that smaller libs are the way to go - we can start > > eventually using a different namespace and releasing the components > > one by one > > We could even do so without using namespaces at all. That's been the > idea behind antlib in the first place. This and easy deployment so > that people stop thinking that Ant must include all tasks on earth > with its default distribution. I agree. At least for a transition period we should use only the local name, even if namespace is enabled. But if we split optional in antlibs, it doesn't hurt to 'name' each group component with a unique name - and use that as 'namespace URI'. > > We can keep the old libs in the system classpath, and release > > tasks in a new package ( org.apache.ant.something ) - as antlibs. > > This is what I wanted to say, yes. Perfect. I hope you're not -1 on the temporary solution I proposed - of detecting if optional.jar is in the CLASSPATH and replacing the class loader with a non-delegating AntClassLoader for all optionals. This doesn't have to get into 1.6 - it can be used for existing 1.5 only. Costin -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
