You can actually still do this for nested types. Do you think you could show me what you ultimately want syntax to see in a build.xml? I'm sort of interested and might have some feedback that could be helpful.
On 3/26/07, Gilles Scokart <[EMAIL PROTECTED]> wrote:
Finally, I forget about using the datatype. It is more powerful to use an ant task, with an id attribute. This really looks like a datatype, but you have the execute method where you can place the code that you want. Gilles > -----Original Message----- > From: Eric Crahen [mailto:[EMAIL PROTECTED] > Sent: lundi 26 mars 2007 16:31 > To: [email protected] > Subject: Re: ivy instances and ant properties > > On 3/25/07, Xavier Hanin <[EMAIL PROTECTED]> wrote: > > > > 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. > > > > I've done quite a bit with ant so if you give me a slight bit more context > I > can give you an answer. > > > -- > > - Eric
-- - Eric
