On 24 May 2002, Stefan Bodewig wrote: > On Fri, 24 May 2002, <[EMAIL PROTECTED]> wrote: > > > Also for Conor - I really want to keep the magic property > > for backward compatibility ( so a build.xml for 1.5 can > > be used with 1.4 ). > > (Even though I'm not Conor 8-)
:-) > The biggest problem I see with a magic property approach is its global > nature. It will be applied for all taskdefs and typedefs of your > project (and those you call with <ant*>), you loose the choice. Would adding 2 attribute, one to force a new classloader and one to force a specific loader disambiguate the problem ? If someone _wants_ a new class loader ( to get around statics ), it should be clear from the build.xml. If someone _wants_ to use a specific loader for the taskdef, it should also be explicit. The default behavior was never specified or documented - and the situation is symetrical. The magic property will just change the default behavior, and again - it is just a way to allow an easy transition from 1.4 to 1.5. We have enough headache with the transition from JDK1.3 to JDK1.4. Luckily ant1.5 doesn't require changes in an ant1.4 build.xml, so this particular transition should be easier. Costin -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
