Costin Manolache wrote: [...] > The behavior will be to load the tasks just like today, and eventually > generate errors on name conflicts ( with a message that if you have > conflicts you must use namespaces - you are no longer in the "simple" > case ). +1 simple and effective IMHO >>This means the build file depends on the user's config to some extent. One >>user has no colision and uses whilst another does and get the >>wrong defined first. Not sure this is good. > > > Yes, if the user has a simple config with non-conflicting antlibs - he'll > have a simpler build file. He'll still declare what antlibs it uses, and > if we detect a conflict we can inform him that the simple times have ended > and he must use namespaces ( at least for the antlibs with conflicts ). Yup. -- Nicola Ken Barozzi nicolaken@apache.org - verba volant, scripta manent - (discussions get forgotten, just code remains) --------------------------------------------------------------------- -- To unsubscribe, e-mail: For additional commands, e-mail: