> From: Jacob Kjome [mailto:[EMAIL PROTECTED]
> > Also, glad to hear import allows you do have a nice generic
> > build file. But what prevents you for putting the Path info
> > in the lightweight importing build file then? It's the project
> > specific build file at this point, no?
>
> Yes, but I
Quoting Dominique Devienne <[EMAIL PROTECTED]>:
> Sorry for missing the point again ;-)
No problem. I appreciate that you took the time to answer :-)
>
> XML or .properties syntax for properties *is* irrelevant.
> But defining Ant paths in XML properties files is not.
Debateable
> This
> was a
> From: Jacob Kjome [mailto:[EMAIL PROTECTED]
>
> Now, to the original point of 's defined in not
> working like
> defined elsewhere. I define my dependencies in an
> file
> and make use of the ability to define 's in that same
> file.
> It keeps things together and keeps my main build file
Quoting Dominique Devienne <[EMAIL PROTECTED]>:
> > From: Jacob Kjome [mailto:[EMAIL PROTECTED]
> >
> > I'm not 100% sure this is a bug, or just a known limitation of
> > , but I'll give it a go and see what others think (I'm
> using
> > Ant-1.6.2, btw)...
>
> Jacob, isn't kind of superseded by ?
> From: Jacob Kjome [mailto:[EMAIL PROTECTED]
>
> I'm not 100% sure this is a bug, or just a known limitation of
> , but I'll give it a go and see what others think (I'm
using
> Ant-1.6.2, btw)...
Jacob, isn't kind of superseded by ?
I've never used the former, so maybe I'm missing what it's
goo
I'm not 100% sure this is a bug, or just a known limitation of
, but I'll give it a go and see what others think (I'm using
Ant-1.6.2, btw)...
When I use to define a path and include a reference to a path
that I override later, if that overridden path includes a pathelement using
a property t
