ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Puzzle" <puz...@puzzlepalace.com>
Subject RE: Using <ant> target with logfile option results in duplicate output
Date Wed, 08 Nov 2000 18:30:01 GMT
I would agree that this seems to be the best solution (at least for me it
would be)


Huw

> -----Original Message-----
> From: Kevin Toomey [mailto:toomeykh@yahoo.com]
> Sent: 08 November 2000 16:09
> To: ant-user@jakarta.apache.org
> Subject: Re: Using <ant> target with logfile option results in duplicate
> output
>
>
> My "all Ant development should revolve around my needs" answer, is to
> change the behavior so that <ant> messages are not considered part of
> the parent build if "output=" is specified.
>
> Thanks,
>
> Kevin
>
> --- Stefan Bodewig <bodewig@bost.de> wrote:
> > Kevin Toomey <toomeykh@yahoo.com> wrote:
> >
> > > I have a buildfile, called build.xml. I execute it from a script
> > > file like so: ant -logfile a_log.txt
> >
> > >    <ant target="server_start" output=b_log.txt />
> >
> > > Instead, all the build info, as well as server output, is written
> > to
> > > a_log.txt. Server output alone, is also written to b_log.txt.
> >
> > Yes, the messages of <ant> are considered part of the parent build as
> > well, therefore they end up in the same logfile as all the other
> > messages. Obviously this is not what everybody would expect.
> >
> > Should we clarify the docs, modify the behavior or what would be the
> > right thing to do?
> >
> > Stefan
>
>
> __________________________________________________
> Do You Yahoo!?
> Thousands of Stores.  Millions of Products.  All in one Place.
> http://shopping.yahoo.com/


Mime
View raw message