I'd like to see some mechanism how to control or filter-out what output is
logged from tasks. There are several verbosity levels etc, but there are
cases when nothing helps.
Example: Recently I came around exec where I executed tool which wrote
bunch of messages to stderr. Nant copy all stderr
On Wed, Oct 26, 2011 at 6:33 PM, Ryan Boggs rmbo...@gmail.com wrote:
Hi,
On Wed, Oct 26, 2011 at 8:53 AM, Stefan Bodewig
stefan.bode...@freenet.de wrote:
On 2011-10-26, Ryan Boggs wrote:
Now that 0.91 final is out the door, I would like to start discussing
what items to work on in both
Hi,
Thanks for your comments, see below.
On Wed, Oct 26, 2011 at 10:57 AM, Leszek Ciesielski skol...@gmail.com wrote:
On Wed, Oct 26, 2011 at 6:33 PM, Ryan Boggs rmbo...@gmail.com wrote:
Hi,
On Wed, Oct 26, 2011 at 8:53 AM, Stefan Bodewig
stefan.bode...@freenet.de wrote:
On 2011-10-26,
I'll avoid the athon and just reply at the top.
+1 on git and github. That's more-or-less the lingua franca of
open-source now-a-days. Being able to accept pull
requests would be awesome! Once it's
there, I've got a heap ton of pull requests I'd love to hand off. To that end,
we should
Ryan,
Towards #net_4, I'd like to see an official download package for each runtime
we target. E.g. one download for .net 1 (the one we have now ... until we kill
it off), .net 2, .net 4, mono vX, mono vY, etc -- e.g. a download per #define
tag. Right now the only way to get a #net_4 runtime
Hi,
On Wed, Oct 26, 2011 at 1:05 PM, Rob Richardson erobr...@yahoo.com wrote:
Ryan,
Towards #net_4, I'd like to see an official download package for each runtime
we target. E.g. one download for .net 1 (the one we have now ... until we
kill it off), .net 2, .net 4, mono vX, mono vY, etc
Hi all,
Thanks for the feedback so far. It's really great to hear all your
thoughts on these matters. Please feel free to tell us your thoughts,
if you haven't already.
I went ahead and converted this list to a page on NAnt's wiki for
easier review and maintenance. I have also made some
Hi Ryan,
+1 for github.
And we should define/discus a contribution process to ensure that nant
core will stay as stable as it is currently.
Other proposals:
- Color output. Red for errors, yellow for warning and green for
sucessfull build. I added this to my own net_2.0 build and I'm
Hey Dominik,
On Wed, Oct 26, 2011 at 2:35 PM, Dominik Guder o...@guder.org wrote:
Hi Ryan,
+1 for github.
How many responses should we collect before we make an official
decision on this? :)
And we should define/discus a contribution process to ensure that nant
core will stay as stable as
