Hi Stefan, no new threads here. It turned out to be
completely related to the placement of the junit task:
<target ..> <target ..>
<junit printsummary="yes" <my-task>
haltonerror="true"> </target>
<formatter type="plain"
usefile="false" />
..
</junit>
<my-task>
</target>
my-task output my-task output
gets lost is shown
I ran out of time to debug the problem, so my workaround
was to add fork="true" to the junit task.
Then the output of my-task is shown.
If my hunch is right, *any* task that writes to stdout
will not work correctly when following a non-forked
junit.
Keith
| -----Original Message-----
| From: Stefan Bodewig [mailto:[EMAIL PROTECTED]
| Sent: Thursday, June 20, 2002 3:19 AM
| To: [EMAIL PROTECTED]
| Subject: Re: differences in target / depends
|
|
| On Wed, 19 Jun 2002, Keith Wannamaker <[EMAIL PROTECTED]> wrote:
|
| > The custom task writes to stdout (which I get in
| > both cases) then calles a java class via introspection
| > (Method.invoke). This called class writes to stdout.
|
| Are you spawning any threads here?
|
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
