On 3/24/07, Gilles Scokart <[EMAIL PROTECTED]> wrote:
I have found an additional issue with the <ivy:settings> dataype replacing the <ivy:configure>: When loading of the ivy.properties file ? This was currently done at the beguining of the configure task. I will try to do it as soon as the datatype is attached to a project. I guess it is the earlier that I can do, and I hope it will still allow to predefine properties with a property task placed before the declaration of the ivy:settings. am I right?
I think so, but I don't know Ant datatypes very well, so I don't know if this can be a source of a problem or not. Maybe you could ask on ant list unless an ant expert reads this thread and can answer directly. - Xavier Gilles
2007/3/24, Gilles Scokart <[EMAIL PROTECTED]>: > 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? > > 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? > > -- > Gilles SCOKART > -- Gilles SCOKART
