--- Stefan Bodewig <[EMAIL PROTECTED]> wrote:
> On Thu, 31 Aug 2006, Matt Benson
> <[EMAIL PROTECTED]> wrote:
>
> > All: shouldn't Ant have an e.g. task?
>
> We probably never felt the need for it, but why not.
> I'm not sure
> about the name since copy implies cloning to me.
> Something with
On Thu, 31 Aug 2006, Matt Benson <[EMAIL PROTECTED]> wrote:
> All: shouldn't Ant have an e.g. task?
We probably never felt the need for it, but why not. I'm not sure
about the name since copy implies cloning to me. Something with
"alias" in its name?
Stefan
--
--- Dominique Devienne <[EMAIL PROTECTED]> wrote:
> >
>
> I agree it's diserable, but it's indeed not
> currently possible to
> override a reference and at the same time reuse the
> previous
> definition, if any. You can do the override alone,
> albeit with a
> warning. This is hurting Ant's ab
I agree it's diserable, but it's indeed not currently possible to
override a reference and at the same time reuse the previous
definition, if any. You can do the override alone, albeit with a
warning. This is hurting Ant's ability to define generic and reusable
build files.
When I designed a
--- Dominique Devienne <[EMAIL PROTECTED]> wrote:
> On 8/31/06, Matt Benson <[EMAIL PROTECTED]>
> wrote:
> > DD, what was that task you had for doing something
> > with references at a different time than Ant
> normally
> > would? Seems like it is attached to a BZ issue
> > someplace... Do you k
On 8/31/06, Matt Benson <[EMAIL PROTECTED]> wrote:
DD, what was that task you had for doing something
with references at a different time than Ant normally
would? Seems like it is attached to a BZ issue
someplace... Do you know what I'm talking about?
Yes, it's called , and is indeed attached
