On 3/24/07, Gilles Scokart <[EMAIL PROTECTED]> wrote:
From what I see, when we call configure, all the ant properties defined at that moment are copied into the ivy engine. In the context of IVY-366, I think it doesn't work anymore. What I would like to do is to 'configure' the ivy instance lazily (only the first time that the corresponding setting is used), and I would find it strange to take the properties at that moment. What I plan to do is to inject an object into the IvySettings class that implements the getVariable by accessing the project. By doing so, the properties considered in every task will be the ant properties defined at the time the task is executed. I don't think that could break some build, but I'm not sure. What do you think?
It sounds like a good idea. One thing to remember, Ivy core doesn't depend on Ant, so make sure you don't introduce a dependency on Ant outside the org.apache.ivy.ant package. Also, I wonder what to do with the variable defined with the task or
inside the settings file. I guess I should not propagate them into the ant properties, and keep them local to ivy. What do you think?
I think they were not propagated before, so they don't need to be propagated. But I'm not absolutely sure, so if you find something strange, please report it here. - Xavier --
Gilles SCOKART
