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
CTED]> wrote in message
news:[EMAIL PROTECTED]
I wanted to lobby for bug 3304 as an enhancement. I have an ant script
which calls subordinate ant scripts using the task. I would like
to pass the build target to the subordinate scripts so they can execute
the same target as the parent (ie. '
sset: throw a BE if the property is set; set the property
Would that help?
Jan
> -Original Message-
> From: Sean Rohead [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, September 24, 2003 1:42 AM
> To: [EMAIL PROTECTED]
> Subject: Bug 3304
>
>
> I wanted to l
I wanted to lobby for bug 3304 as an enhancement. I have an ant script
which calls subordinate ant scripts using the task. I would like
to pass the build target to the subordinate scripts so they can execute
the same target as the parent (ie. 'ant compile' calls the compile
tar
