I think that is a great idea. It should be as simple as
post-processing
the output stream and pre-pending the (indent) spaces at the front of
each
line. It might be easier to create an PrependedStringReader that take
a
string to pre-pend to each line, and the stream to read from. Then we
can
Hi,
I'd love to see the logging system allow me to implement an XML log listener
which can output a simple file that I can transform into a nice XHTML build
log to place straight on the web server.
In addition, on my nightly build machine I could then combine all of the XML
files into one large
Hi,
[see below] Is that the kind of thing you had in mind?
In a way, yes. I was under the impression that all the tasks currently use
the Log class to write their build output, and it might be nice to extend
this to output something a little better defined:
build-results
target-output
Regardless of future implementation tasks, would anyone object if I
enhance the ExternalProgramBase to indent output from called programs? :)
I agree that we need a more powerful logging system, but as things stand
right now, we have a half-decent one that gets the job done. Once 0.8
is
Title: Message
I have two NAnt
build files, with one calling the other. Bothinclude the"sysinfo/" line. When I run the main build file, I get
the following error message. Perhaps you have already fixed this in a later
version.
Randy
Regnier
E:\fw\Bld\XMLnantBuildfile:
Granted, we're getting off topic... but Bill's Kung-Fu is clearly
stronger than mine and I wish to lean. (And figure it might be
instructive to others)
So Bill,
Am I understanding correctly that this defeats the security of scoping
something as private? Are there limits to this? (Like
Strongly in favor of throwing 0.8 against the wall and seeing what
sticks.
Re: logging
What's folks feeling about moving back to the Ant-style loglevel
concept? (quiet, normal, verbose, warning, error). I'd traded some
mail with Scott about log4net, .config files, and other wouldn't it be
Okay, I put in the feature to disable the
autoLookup dotnet task path stuff. It is a major hack, and should be replaced
immediately after the next release. We should get real config support
going...
If you definethe "doNotFind.dotnet.exes"propertyto "true" it will enable
you to run the
I say we call tonight's build the candidate release. (When I get back from
Manhattan and San Francisco, sometime after Monday, I will do the real
build.)
At this point I've changed this to be the 0.8.01.* release. I think we have
confused people enough since we have been floating on the 0.8.0
Bryce,
Which build of nant are you using ? I seem to recall this being fixed a
while ago.
Ian
Using the examples available in the online docs for the 'zip' task as
part of a build script. The ZIP file is created successfully and has the
expected set of files except that the leading 2
10 matches
Mail list logo
