Re: Bug tracker tag for 0.9

Ryan Boggs <[email protected]>
Newsgroups gmane.comp.windows.dotnet.nant.devel
Message-ID <[email protected]>
Hey Richard,

Would you mind giving the latest nightly file a try (04-02-2010)?  We
believe that we were able to fix the output issue you experienced.
Let us know how it works for you.

Thanks,
Ryan

On Thu, Apr 1, 2010 at 1:06 PM, Richard Birkby <[email protected]> wrote:
> Congrats on releasing 0.9a1.
> I immediately put it into our build process and found an issue -
> unfortunately, I can't enter the issue into Nant's bug tracker because a
> 0.9a1 tag is missing - any chance you could add one?
> I also noticed if I click on Releases->0.90 Alpha 1 in the left hand
> navigation bar on the Nant homepage, it takes me to the following page which
> gives an error:
> http://nant.sourceforge.net/release/0.90-alpha1/
> The bug which I was unable to enter is that when I use Nant-Contrib's
> MSBuild task, all output from the task is concatenated onto a single line
> with no carriage returns.
>
> Thanks
> Richard
> ------------------------------------------------------------------------------
> Download Intel&#174; Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> nant-developers mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/nant-developers
>
>

------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.