Hello Nicklas, probably, the best way to fill the gap would be to implement <try/catch/finally> task as it is done in Ant. I considered starting to implement this functionality, but at the time I learnt about the way it is done in Ant, I'd already made the "onfail" patch which we use now in our build-scripts. It allows to call arbitrary task on some task or target failure (you just have to add "onfail='taskToCall'" attribute to the corresponding task/target element). I've sent here this patch, but surely it was not so nice as a solution of the problem, <try/catch/finally> should be a better way.
I have all my projects building with "onfail" patch, and it works, so I gave up trying to do some new thing which no one needs except me. Now probably, the time has come to do such a thing, still, it should be thoroughly though over, how to do it in a right way. ps: see http://ant-contrib.sourceforge.net/tasks/trycatch.html for ant <trycatch> task description. >> -----Original Message----- >> From: Gert Driesen [mailto:[EMAIL PROTECTED] >> Sent: den 27 februari 2004 08:37 >> To: Hemry, Jeff; [EMAIL PROTECTED] >> Subject: Re: [nant-dev] 2 small changes to consider >> >> >> >> > ----- Original Message ----- >> > From: "Hemry, Jeff" <[EMAIL PROTECTED]> >> > To: <[EMAIL PROTECTED]> >> > Sent: Thursday, February 26, 2004 8:48 PM >> > Subject: [nant-dev] 2 small changes to consider >> > >> >> > Hi all, >> > >> > >> > >> > Here are 2 small changes put in place for our specific >> needs that may be >> > beneficial to the whole group. >> > >> > >> > >> > 1) Multiple files: Added a project level variable called >> > nant.project.failure, such that a you can allow a task or >> group of tasks >> > to complete regardless of failure using failonerror=false, and then >> > afterwards check the value of nant.project.failure to determine if a >> > failure occurred. Very useful for batch nunit tests, and gathering a >> > report of the tests before checking if a failure occurred >> and throwing a >> > fail. >> >> Not sure if we should something like this, but we'll give it >> some thought >> ... NN> This points out a gap in nant as I see it. What Jeff has made a patch NN> for is actually a pretty large gap in functionality in nant. NN> Controlling the flow using failure detection and also log that neatly NN> for other tools to pick up (CCNet comes to mind) is challenging to say NN> the least. NN> I for one would love to see some of the big brains storm some on this NN> issue. I've got a pretty good knowledge about what I need, but no matter NN> how much I think about it I can't figure out a good suggestion to come NN> up with. NN> What do the rest of you guys and girls out on the list think about it? NN> Would be interesting to hear your opinions. NN> (Gosh... did I hijack this thread?) NN> /Nicke NN> ------------------------------------------------------- NN> SF.Net is sponsored by: Speed Start Your Linux Apps Now. NN> Build and deploy apps & Web services for Linux with NN> a free DVD software kit from IBM. Click Now! NN> http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click NN> _______________________________________________ NN> nant-developers mailing list NN> [EMAIL PROTECTED] NN> https://lists.sourceforge.net/lists/listinfo/nant-developers -- Best regards, Ivan mailto:[EMAIL PROTECTED] ------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click _______________________________________________ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
