Funny you should say that. That was the default behavior of my submission,
and Steve L. changed that when it moved to Ant ;-) --DD
> -Original Message-
> From: Knut Wannheden [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, September 24, 2003 3:11 AM
> To: [EMAIL PROTECTED]
> S
You are correct. I apologize for not having read the original
enhancement more carefully. I have submitted a new enhancement
(http://issues.apache.org/bugzilla/show_bug.cgi?id=23450) that solves
the problem I have described.
Sean Rohead
<<
On Fri, 26 Sep 2003 02:36 am, Sean
On Fri, 26 Sep 2003 02:36 am, Sean Rohead wrote:
> Thanks for the replies.
>
>
> But I'm still confused about the reluctance to embrace the original
> proposal.
The original proposal does not solve your problem. It adds a property which
changes to the target name currently being executed. If yo
Thanks for the replies.
Unfortunately, the suggested workarounds aren't really ideal either. I don't
want the task to use the current (containing) target, I want the ant task
to use the target that was provided on the command line - otherwise I still
have to put tasks in every top-level tar
Maybe the task could be modified to use the current target (the
target in which the task is contained) as the default, instead of
the called project's default target. That's how my own works and I
think it is a reasonable default.
--
knut
"Sean Rohead" <[EMAIL PROTECTED]> wrote in message
new
Workaround:
target.name=${target.name}
