On 27 May 2002, Stefan Bodewig wrote: > > Would adding 2 attribute, one to force a new classloader and one to > > force a specific loader disambiguate the problem ? > > It would, if you long for 1.5+ only build files. > > You've introduced the magic property to make it possible to write > build files that are compatible with 1.4.1 and 1.5 at the same time, > right? If you use new attributes, you can't do that any longer.
Actually, the attributes are for 1.5+ build files, and I'll use them in build files after 1.5 significantly replace 1.4 ( probably ~ 6 months). Until then - the 'magic' property and no attributes, so the build files will work with 1.4.1 ( unmodified - but with the old restriction that cpptasks.jar must be copied in ant/lib ). > We better advice people that they should not use the magic property at > all but use the loaderref attribute instead - if they can live with > Ant 1.5 build files. I see this magic property as something that > should be deprecated (but we don't do that any longer) right now. I partially agree. Explicit attributes are cleaner than magic properties. Costin -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
