-Original Message-
From: Stefan Bodewig
If so, a simple invocation of
getProject().registerThreadTask(Thread.currentThread(), ant) before
ant.execute() would have done the trick. Hmm,
ant.setTaskName(getTaskName()) would solve the [ant] vs. [subant]
issue.
[DD] This is what I was trying
> From: Stefan Bodewig [mailto:[EMAIL PROTECTED]
>
> On Fri, 2 Jul 2004, Jose Alberto Fernandez <[EMAIL PROTECTED]>
> wrote:
>
> > Maybe Ant should provide its own delegation entry point
> since this is
> > a very common pattern of use.
>
> But maybe not something you want to expose. Do you
On Fri, 2 Jul 2004, Jose Alberto Fernandez <[EMAIL PROTECTED]>
wrote:
> Maybe Ant should provide its own delegation entry point since this
> is a very common pattern of use.
But maybe not something you want to expose. Do you want to see [ant]
show up in the log instead of [subant]?
If so, a sim
27;Stefan Bodewig '; '[EMAIL PROTECTED] '
> Subject: RE: SubAnt output
>
>
> -Original Message-
> From: Stefan Bodewig
>
> On Fri, 2 Jul 2004, Dominique Devienne <[EMAIL PROTECTED]> wrote:
>
> > [DD] What if instead of adding all the
-Original Message-
From: Stefan Bodewig
On Fri, 2 Jul 2004, Dominique Devienne <[EMAIL PROTECTED]> wrote:
> [DD] What if instead of adding all these methods, we called
> [DD] ant.perform() instead of ant.execute()!?
> [DD] perform() fires the the taskStarted event, so would that be
> [DD]
On Fri, 2 Jul 2004, Dominique Devienne <[EMAIL PROTECTED]> wrote:
> [DD] What if instead of adding all these methods, we called
> [DD] ant.perform() instead of ant.execute()!?
> [DD] perform() fires the the taskStarted event, so would that be
> [DD] enough? Would be a lot less code, no?
It would
From: Stefan Bodewig
> I would have thought that executing the nested Ant would have been
> enough to properly nest the messages.
No.
The output is dispatched to the task associated with the thread(group)
- and the association happens when the taskStarted event is fired.
When you delegate to ano
Stefan Bodewig wrote:
On Thu, 1 Jul 2004, Dominique Devienne <[EMAIL PROTECTED]> wrote:
Even though it's a bit late, I would like this patch to make it to
1.6.2. Does anyone object?
It's in, even if it doesn't go into 1.6.2 RC (no idea whether antoine
has started to work on it already).
On Thu, 1 Jul 2004, Dominique Devienne <[EMAIL PROTECTED]> wrote:
> Even though it's a bit late, I would like this patch to make it to
> 1.6.2. Does anyone object?
It's in, even if it doesn't go into 1.6.2 RC (no idea whether antoine
has started to work on it already).
> I would have thought that
I'm not one of the gurus but as far as I understood the mechanism the
logger has to deal with output on standard out and standard error in
addition to the builtin methods which might be called by task
implementations.
In my case we had such a tool (javac) output to standard error. To
identify the c
On Thu, 01 Jul 2004, Christian Knorr <[EMAIL PROTECTED]>
wrote:
> I am new to this list. By browsing the archives I could not find
> anything related to my problem but forgive me if it has already been
> mentioned:
It hasn't. Thanks for the patch!
Stefan
---
Cool. Thanks for fixing this. Even though it's a bit late, I would like this
patch to make it to 1.6.2. Does anyone object?
But on a different note, even though I looked at the patch, I'm not sure I
understand why adding these methods fixes the problem (as was involved in
writing SubAnt.java initi
12 matches
Mail list logo
