What I would like to see:
<copy todir="../new/dir">
<ivy:fileset conf="compile"/>
</copy>
<java classname="test.Main">
<arg value="-h"/>
<classpath>
<ivy:path conf="runtime"/>
<pathelement path="${java.class.path}"/>
</classpath>
</java>
But also maybe:
<ivy:resolve file="ivy.xml">
<ivy:settings file="path/to/ivysettings.xml" />
</ivy:resolve>
Or even the maybe ugly:
<ivy:retrieve conf="runtime">
<ivy:resolve file="ivy.xml">
<ivy:settings file="path/to/ivysettings.xml" />
</ivy:resolve>
</ivy:retrieve>
I see a real added value for the first example. For the two other ones, I'm
not sure it's really better than setting an id when you call configure, and
then using this settings id when you call resolve (or anything else).
WDYT?
- Xavier
On 3/26/07, Eric Crahen <[EMAIL PROTECTED]> wrote:
That's why I think we should start with what do we want to see in a
build.xml. We can work backwards and figure out what it would take to get
us
there...
On 3/26/07, Xavier Hanin <[EMAIL PROTECTED]> wrote:
>
> I'm interested too, not that I see a strong benefit of converting this
> task
> to a datatype, but more that I'm wondering about converting other tasks
> (like cachepath and cachefileset) to datatypes, and thus I'm interested
in
> feedback about your experience.
>
> - Xavier
>
> On 3/26/07, Eric Crahen <[EMAIL PROTECTED]> wrote:
> >
> > 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
> >
>
--
- Eric
