On Wed, Feb 22, 2012 at 11:46 PM, Richard Birkby <rbirkby@gmai...> wrote:
> Sounds great. Looking forward to it.
> For me, the big omission from the current nunit task has been /label
> support so I can figure out which failing test produced the exceptions
> in our 2MB of test/build output.
> I have had a look at the branch, but it doesn't look like it supports
> /label. Is that correct?
Yeah, I was more worried about getting the new version of NUnit
working with NAnt than adding features. However, I just took a look
in NUnit's console setup for the label argument. Implementing this
seems pretty easy enough and the impact on how the task runs is
minimal. Just need to make sure it looks ok when it is printed. I'll
see about adding this today. Thanks for the tip. :)
> Additionally, while I don't use the style task, I notice you aren't caching
> the compiled XSL transform between runs. This means you will incur a compile
> on every invocation. This will kill performance for users transforming many
Hmm, good observation. I'll take a look and see what's needed to get
the caching going for this task.
> On Thu, Feb 23, 2012 at 4:31 AM, Ryan Boggs <rmboggs@gmai...> wrote:
>> Hi all,
>> Just checking in with some progress that has been occurring in NAnt's
>> development. It's not a complete list but there are a few big ones
>> that I think are worth highlighting.
>> * The VS project solution files for both NAnt and NAntContrib projects
>> have been updated to VS2010 format.
>> * .NET/Mono 1.* runtime support for NAnt has been dropped. Target
>> support for .NET/Mono 1.* still exists, however.
>> * The <style/> task has been updated to use xslCompiledTransform,
>> which should address the issue described here on Stackoverflow:
>> http://stackoverflow.com/questions/5032347/xslt-stylesheet-replaces-self-closing-tags-with-empty-paired-tags >> Thanks to Michael Tutty for the contribution via pull request for this
>> * The <mail/> task has been updated to use System.Net.Mail instead of
>> System.Web.Mail. During the process of updating this task, additional
>> features were added that we thought to be very helpful (such as
>> specifying a reply to address, specifying the port number to send mail
>> to, indicating whether or not to use an ssl connection, etc).
>> * More work has gone into the <msbuild/> with the help from Dominik
>> Guder and Martin Aliger. From what I understand, there are still a
>> couple of outstanding issues with this item but the task is working
>> better with recent versions of msbuild scripts. This is still a high
>> * Quite a bit of work has been put into upgrading the <nunit2/> task
>> to reference the latest version of NUnit. I'm happy to say that these
>> changes are currently in review to be imported into nant/master. The
>> version of NUnit being used for this upgrade is 2.6 final (which was
>> released just a few days ago). I'm hoping that this will go into
>> master soon. I want to say thanks to Charles Poole and the rest of
>> the NUnit dev team for their help and insight to get the <nunit2/> up
>> to speed. They were very helpful in this process. Anyone interested
>> in viewing these changes can see them here:
>> https://github.com/nant/nant/tree/nunitupdates >>
>> * The nightly process for both NAnt and NAntContrib projects have
>> started up again. This time, an automated process has been setup with
>> extensive help from Dominik Guder to make sure that new nightly files
>> are generated whenever changes occur on the master branches of either
>> project. The last nightly was built on 2/19/2012 and includes all the
>> changes listed above except for the nunit changes. The nightly files
>> can be found in the following locations:
>> NAnt Nightlys:
>> https://sourceforge.net/projects/nant/files/nant/nightly/ >>
>> NAntContrib Nightlys:
>> https://sourceforge.net/projects/nantcontrib/files/nantcontrib/nightly/ >>
>> We are still trying to nail down release dates and should be
>> announcing them as soon as they are finalized.
>> The next version number being targeted for NAnt/NAntContrib is
>> currently 0.92. It seems like the natural progression but we are
>> curious if you have any reasons to use a different version number (ie:
>> should we skip 0.92 and go to 0.95, etc).
>> That's all I have for now. I will try to send out these kinds of
>> notices more often as progress continues.
>> Virtualization & Cloud Management Using Capacity Planning
>> Cloud computing makes use of virtualization - but cloud computing
>> also focuses on allowing computing to be delivered as a service.
>> http://www.accelacomm.com/jaw/sfnl/114/51521223/ >> _______________________________________________
>> nant-developers mailing list
>> nant-developers@list... >> https://lists.sourceforge.net/lists/listinfo/nant-developers >
> Virtualization & Cloud Management Using Capacity Planning
> Cloud computing makes use of virtualization - but cloud computing
> also focuses on allowing computing to be delivered as a service.
> http://www.accelacomm.com/jaw/sfnl/114/51521223/ > _______________________________________________
> nant-developers mailing list
> nant-developers@list... > https://lists.sourceforge.net/lists/listinfo/nant-developers >