On Wed, 12 Dec 2001, Jose Alberto Fernandez <[EMAIL PROTECTED]> wrote:
> What I am saying is to modify the thing so that <param> means the > same thing everywhere (<ant> and <antcall>). Which meant that <param> on <antcall> in Ant 1.5 would behave different from the one in 1.4.1 - no way. > This is the "when a BUG becomes a feature" syndrome. > [...] With that philosophy it is very difficult to produce a good > consistent tool. This is where the cat for Ant2 is expected. We are doomed with backward compatibility within the 1.x family. > From: "Stefan Bodewig" <[EMAIL PROTECTED]> > >> > 1) If I remember correctly, datatypes are associated to a Project >> > instance during creation. >> >> Most of them still take an explicit project instance when you use >> them. But we need to take care here, you are correct. > > I am not saying it is wrong for them to be evaluated in the context > of their original Project After thinking about it again, it seems that passing clones (with the new project as a reference) would be the way to go - otherwise changes made to the referenced objects in the subbuild would change the objects in the parent build at the same time. Stefan -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
