[nant-dev] onsuccess / failure
Hi, Is it ok to rename the properties that designates a target to execute when the build fails from nant.failure to nant.onfailure, to have it in sync with nant.onsuccess ? I know this is a breaking change, so we should document it as such in the release notes. In my opinion, changes like these should still be allowed, as long as they're clearly documented. Gert --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0016ave/direct;at.asp_061203_01/01 ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
Re: [nant-dev] Branch for 0.8.3.xxx release
Hi John, I've created a branch and named it BRANCH-083, as a tag has to start with a letter and cannot contain dots. Gert On Thu, 2003-07-03 at 03:46, John Barstow wrote: Now that we have a cleanly building code base, can someone with CVS write access create a branch for the 0.8.3 release? The command to run in the working directory is: cvs tag -b branch-0-8-3 After running the command, you will still be on the main branch and should increment the default build number to 0.8.4. Release notes, bug fixes, et al will go on the branch, and be merged back into the main trunk after the release ships. I'll also request a branch of NAntContrib after the tests build cleanly. John C Barstow --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0016ave/direct;at.asp_061203_01/01 ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0016ave/direct;at.asp_061203_01/01 ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
Re: [nant-dev] Branch for 0.8.3.xxx release
I forgot : I'll increment the version number later today ... what version number do you recommend, 0.8.4. ? what was actually decided after the discussion on this subject ? John, will you assign a fixed (0.8.3.x) version number to the 0.8.3 branch before building the release ? will you be creating a test-release first (I'd recommend that), adn alow us to access that ? Gert On Thu, 2003-07-03 at 03:46, John Barstow wrote: Now that we have a cleanly building code base, can someone with CVS write access create a branch for the 0.8.3 release? The command to run in the working directory is: cvs tag -b branch-0-8-3 After running the command, you will still be on the main branch and should increment the default build number to 0.8.4. Release notes, bug fixes, et al will go on the branch, and be merged back into the main trunk after the release ships. I'll also request a branch of NAntContrib after the tests build cleanly. John C Barstow --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0016ave/direct;at.asp_061203_01/01 ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0016ave/direct;at.asp_061203_01/01 ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
Re: [nant-dev] NAntContrib tests do not build
rather than comment out that reference try building with :
nant -D:nant.dir=C:\cvs\nant\build\nant-0.8.3-debug
if you've just built a new NAnt from source then
C:\cvs\nant\build\nant-0.8.3-debug\bin\ will contain
NAnt.Core.Tests.dll, satisfying the reference.
Ian
Ian MacLean writes:
they are building now but not yet passing for me. Missing dependency
issues. I'll look into it.
Attached is a patch that partially fixes the build issue.
Note that /NAntContrib/Tests/Tasks/TlbImpTaskTest.cs still does not compile
due to an actual dependency on Tests.Nant.Core (derives from the test base
class).
John C Barstow
--
Index: Tests/Alltests.cs
===
RCS file: /cvsroot/nantcontrib/NAntContrib/Tests/Alltests.cs,v
retrieving revision 1.4
diff -u -r1.4 Alltests.cs
--- Tests/Alltests.cs 2 Jul 2003 01:06:02 - 1.4
+++ Tests/Alltests.cs 3 Jul 2003 02:02:55 -
@@ -27,7 +27,7 @@
using NUnit.Framework;
using NAnt.Core.Attributes;
using NAnt.Core;
-using Tests.NAnt.Core;
+//using Tests.NAnt.Core;
namespace NAnt.Contrib.Tests {
Index: Tests/Tasks/TlbImpTaskTest.cs
===
RCS file: /cvsroot/nantcontrib/NAntContrib/Tests/Tasks/TlbImpTaskTest.cs,v
retrieving revision 1.4
diff -u -r1.4 TlbImpTaskTest.cs
--- Tests/Tasks/TlbImpTaskTest.cs 2 Jul 2003 01:06:02 - 1.4
+++ Tests/Tasks/TlbImpTaskTest.cs 3 Jul 2003 02:02:56 -
@@ -24,7 +24,7 @@
using System.Xml;
using NUnit.Framework;
-using Tests.NAnt.Core;
+//using Tests.NAnt.Core;
namespace NAnt.Contrib.Tests {
Index: Tests/Util/SqlStatementListTests.cs
===
RCS file:
/cvsroot/nantcontrib/NAntContrib/Tests/Util/SqlStatementListTests.cs,v
retrieving revision 1.8
diff -u -r1.8 SqlStatementListTests.cs
--- Tests/Util/SqlStatementListTests.cs 2 Jul 2003 01:06:02 - 1.8
+++ Tests/Util/SqlStatementListTests.cs 3 Jul 2003 02:02:56 -
@@ -29,7 +29,7 @@
using NAnt.Core;
using NAnt.Contrib.Util;
-using Tests.NAnt.Core;
+//using Tests.NAnt.Core;
namespace NAnt.Contrib.Tests.Util {
/// summary
---
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa0016ave/direct;at.asp_061203_01/01
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers
---
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa0016ave/direct;at.asp_061203_01/01
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers
[nant-dev] Re: [NAntC-Dev] NAnt.Optional.zip
sorry for the confusion but : we decided to keep the tasks in NAntcontrib for now and move a bunch of them into nant - post 0.83 release - see the 'Namespaces and NAnt.Cnntrib tasks' post for details on what tasks will go where. but don't worry the bullet remains bitten. I've rolled the changes that are in NAnt.optional.zip back into nantcontrib which is now building against current NAnt cvs. We will ship a nant contrib task assembly with nant for the upcoming release. Nick: But the record task doesn't work, it simply create an empty file and doesn't loag anything into it. Since I have an updated version, which works with the new logging system, i could sent it to you, after making some minors changes to reflect the namespace changes. that would be awesome. All I did was comment stuff until it compiled. If you have a version that works with the new logging system just send it to me and I'll commit. Another thing, I had to move the dll's from the bin\optional directly into bin to have NAnt recognize the tasks. It should find them there. Are you running nant from \build\nant-0.8.3-debug\bin and does the nant.exe.config in that directory contain : nantsettings defaultframework=net-1.0 taskpath=.\optional taskpath allows you specify a ';' seperated list of directories that contain task assemblies. You may need to cvs update nant as well to get the taskpath related changes. Ian further 2 cents: 1) thanks for biting the bullet, very much! 2) does it make sense that nantcontrib ends up in a single dll as opposed to several dlls, smaller, per task set? seems to me it might complicate the configuration a little bit more, but would yield easier to handle subproject (eg: if one task is broken, the whole thing isn't broken...) /jean -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of N. V. Sent: Wednesday, July 02, 2003 17:37 To: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: [NAntC-Dev] NAnt.Optional.zip Hi Ian, I just tested this, with my build files which uses vssget, sql and record task and the vssget and sql task works fines (i prefered when the sql task wasn't writting every params to the the Console, but that's not really a problem). Another thing, I had to move the dll's from the bin\optional directly into bin to have NAnt recognize the tasks. Nick From: Ian MacLean [EMAIL PROTECTED] To: [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: [NAntC-Dev] NAnt.Optional.zip Date: Sun, 29 Jun 2003 20:08:22 +0900 grab it from http://www26.brinkster.com/ianm74/NAnt.Optional.zip unzip it under nant\src and add the following line to TaskAssemblies.txt : NAnt.Optional then just run the main nant build. this creates a new folder optional under build\nant-0.8.3-debug\bin with the optional tasks dll and its dependencies. If you run the newly built NAnt it will load the optional tasks as well as the core ones. I just got it compiling and tested a few of the tasks. Please try it out and let me know if anything is broken. Ian --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0016ave/direct;at.asp_0 61203_01/0 1 ___ NAntContrib-Developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nantcontrib-developer _ MSN Messenger : discutez en direct avec vos amis ! http://messenger.fr.msn.ca/ --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0016ave/direct;at.asp_06 1203_01/01 ___ NAntContrib-Developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nantcontrib-developer --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0016ave/direct;at.asp_061203_01/01 ___ NAntContrib-Developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nantcontrib-developer --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals,
Re: [nant-dev] Branch for 0.8.3.xxx release
On Thu, 2003-07-03 at 04:13, Gert Driesen wrote: I forgot : I'll increment the version number later today ... what version number do you recommend, 0.8.4. ? what was actually decided after the discussion on this subject ? 0.8.4.xxx for the main branch. Typically, the suggestion is to increment after a release, but I don't want any confusion between the 0.8.3 candidates and the main branch. John, will you assign a fixed (0.8.3.x) version number to the 0.8.3 branch before building the release ? Yes, I will. There will be a fixed number for each release candidate as well as the final 0.8.3.xxx release. will you be creating a test-release first (I'd recommend that), adn alow us to access that ? Absolutely. As soon as I have clean compiles of Nant and NantContrib I will prep a candidate release and make it publicly available for a decent amount of time (probably a week). John C Barstow (home) signature.asc Description: This is a digitally signed message part
Re: [nant-dev] Branch for 0.8.3.xxx release
On Thu, 2003-07-03 at 05:38, Gert Driesen wrote: Apparently, for previous releases a branch was make named rel-version number eg. rel-0-8-3 perhaps we should use the same naming scheme for the 0.8.3 branch ... I intend to use the rel-0-8-3 tag for the final 0.8.3 release; I may have misunderstood but I though previous releases were tagged (as opposed to branched). Can we start committing to the main branch now ? Yes, go ahead and commit anything you've been holding off on to the main branch. There will be an 0.8.4 release sometime around the first week of August. Please don't commit to NAntContrib until that is also branched; that should happen tomorrow as Ian has explained how to compile the tests. John C Barstow --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0016ave/direct;at.asp_061203_01/01 ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
[nant-dev] CVS build of nant fails when building nant
I have nant from a daily build installed (2003-06-21) and I try to build nant (cvs version) from it, I get the following result [exec] C:\Projects\3rdParty\nant-cvs/build/nant-0.8.3-debug/bin/NAnt.exe buildfile:NAnt.build debug self-test -D:project.version=0.8.3 -k:net-1.1 Unhandled Exception: System.Configuration.ConfigurationException: E ror loading XML file c:\winnt\microsoft.net\framework\v1.0.3705\Config\machine. onfig Request for the permission of type System.Security.Permissions.StrongName dentityPermission, mscorlib, Version=1.0.3300.0, Culture=neutral, PublicKeyToke =b77a5c561934e089 failed. (c:\winnt\microsoft.net\framework\v1.0.3705\Config\ma hine.config) at System.Configuration.ConfigurationRecord.OpenXmlTextReader(St ing configFileName) at System.Configuration.ConfigurationRecord.Load(String filename at System.Configuration.DefaultConfigurationSystem.System.Config ration.IConfigurationSystem.Init() at System.Configuration.ConfigurationSettings.SetConfigurationSy tem(IConfigurationSystem configSystem) at System.Configuration.ConfigurationSettings.GetConfig(String s ctionName) at System.Configuration.ConfigurationSettings.get_AppSettings() at NAnt.Console.ConsoleStub.Main(String[] args) in c:\Projects\3 dParty\nant-cvs\src\NAnt.Console\ConsoleStub.cs:line 44 Total time: 6 seconds. BUILD FAILED C:\Projects\3rdParty\nant-cvs\NAnt.build(120,10): External Program Failed: C:\Projects\3rdParty\nant-cvs/build/nant-0.8.3-debug/ in/NAnt.exe (return code was -532459699) BUILD FAILED The only thing I did was set net-1.1 as the default inside the nant.exe.config file (from daily build). Philippe Lavoie Cactus Commerce eBusiness. All Business. Tel 819.778.0313 x302 888.CACTUS.0 Fax 819.771.0921 www.cactuscommerce.com [EMAIL PROTECTED]
RE: [nant-dev] Bug in solution task with a web project
That did the trick, I added vbc (by contract, not choice) to the path and now it got a lot further. However, now it's stuck with the following which I hope is now fixed inside CVS (except that I can't compile CVS... ) Web_IClicWeb.vbproj\Global.asax.resx Total time: 0 seconds. BUILD FAILED INTERNAL ERROR System.ArgumentException: Can't parse VB files yet at NAnt.VSNet.Tasks.Resource.GetDependentResourceName(String strDependentFile ) at NAnt.VSNet.Tasks.Resource.CompileResx() at NAnt.VSNet.Tasks.Resource.Compile(ConfigurationSettings cs, Boolean bShowC ommands) at NAnt.VSNet.Tasks.Project.Compile(String strConfiguration, ArrayList alCSCA rguments, String strLogFile, Boolean bVerbose, Boolean bShowCommands) at NAnt.VSNet.Tasks.Solution.Compile(String strConfiguration, ArrayList alCSC Arguments, String strLogFile, Boolean bVerbose, Boolean bShowCommands) at NAnt.VSNet.Tasks.SolutionTask.ExecuteTask() at NAnt.Core.Task.Execute() at NAnt.Core.Target.Execute() at NAnt.Core.Project.Execute(String targetName) at NAnt.Core.Project.Execute() at NAnt.Core.Project.Run() Please send bug report to [EMAIL PROTECTED] Philippe Lavoie Cactus Commerce eBusiness. All Business. Tel 819.778.0313 x302 * 888.CACTUS.0 * Fax 819.771.0921 www.cactuscommerce.com [EMAIL PROTECTED] -Original Message- From: Matthew Mastracci [mailto:[EMAIL PROTECTED] Sent: Thursday, July 03, 2003 12:07 PM To: Philippe Lavoie Cc: [EMAIL PROTECTED] Subject: Re: [nant-dev] Bug in solution task with a web project Is CSC.EXE in your path while running NAnt? I'm hoping one day to add a web path mapping property to the solution task. Right now it has a very basic set of error-prone WebDAV methods to handle compiling of a web project that is usually on the build server anyways. It also tries to use the credentials of the logged-in user. Microsoft uses the FrontPage extensions to work around these problems. It seems to work better with IIS. Philippe Lavoie wrote: I wanted to use slingshot and for some reason it would load (and it doesn't work with VS 2003 anyway). Then, I noticed that the solution might be the way to go. I added a simple solution task to my build system ?xml version=1.0? project name=App default=build property name=debug value=true/ property name=build.basedir value=Build / target name=build solution configuration=debug solutionfile=source/App.sln/ /target /project The first time I was getting a 403 error (the web project is a virtual directory which points back inside my source directory). Fixed that by adding a checkbox to every permission available inside that directory. Then I ran the script again and got Nant -debug http://localhost/AppWeb/FixedTermLoan/Product.aspx.vb http://localhost/AppWeb/FixedTermLoan/Product.aspx.resx [solution] Building APP [debug]... [solution] Copying references: [solution] - System [solution] - System.Data [solution] - Microsoft.ApplicationBlocks.Data [copy] Copying 0 files to C:\Projects\App-dev\Latest\source\L ibrary\APP\bin\. [solution] - System.XML [solution] Compiling resources: [solution] Starting compiler... Total time: 0 seconds. BUILD FAILED INTERNAL ERROR System.ComponentModel.Win32Exception: The system cannot find the file specified at System.Diagnostics.Process.StartWithCreateProcess(ProcessStartInfo startIn fo) at System.Diagnostics.Process.Start() at System.Diagnostics.Process.Start(ProcessStartInfo startInfo) at NAnt.VSNet.Tasks.Project.Compile(String strConfiguration, ArrayList alCSCA rguments, String strLogFile, Boolean bVerbose, Boolean bShowCommands) at NAnt.VSNet.Tasks.Solution.Compile(String strConfiguration, ArrayList alCSC Arguments, String strLogFile, Boolean bVerbose, Boolean bShowCommands) at NAnt.VSNet.Tasks.SolutionTask.ExecuteTask() at NAnt.Core.Task.Execute() at NAnt.Core.Target.Execute() at NAnt.Core.Project.Execute(String targetName) at NAnt.Core.Project.Execute() at NAnt.Core.Project.Run() Please send bug report to [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]. I'm using the latest snapshot available 20030621 (as the CVS source available from anonymous don't want to build. I'll send another report for that.) I wish I knew more what the problem was, since it seems I won't be able to use nant until this is fixed... Philippe Lavoie Cactus Commerce eBusiness. All Business. Tel 819.778.0313 x302 * 888.CACTUS.0 * Fax 819.771.0921 www.cactuscommerce.com [EMAIL PROTECTED] --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0016ave/direct;at.asp_061203_01/01 ___ nant-developers mailing list [EMAIL
Re: [nant-dev] Bug in solution task with a web project
Someone posted a patch for this item earlier... I don't know if it was ever applied. I can look and make sure it's in CVS. Philippe Lavoie wrote: That did the trick, I added vbc (by contract, not choice) to the path and now it got a lot further. However, now it's stuck with the following which I hope is now fixed inside CVS (except that I can't compile CVS... ) Web_IClicWeb.vbproj\Global.asax.resx Total time: 0 seconds. BUILD FAILED INTERNAL ERROR System.ArgumentException: Can't parse VB files yet at NAnt.VSNet.Tasks.Resource.GetDependentResourceName(String strDependentFile ) at NAnt.VSNet.Tasks.Resource.CompileResx() at NAnt.VSNet.Tasks.Resource.Compile(ConfigurationSettings cs, Boolean bShowC ommands) at NAnt.VSNet.Tasks.Project.Compile(String strConfiguration, ArrayList alCSCA rguments, String strLogFile, Boolean bVerbose, Boolean bShowCommands) at NAnt.VSNet.Tasks.Solution.Compile(String strConfiguration, ArrayList alCSC Arguments, String strLogFile, Boolean bVerbose, Boolean bShowCommands) at NAnt.VSNet.Tasks.SolutionTask.ExecuteTask() at NAnt.Core.Task.Execute() at NAnt.Core.Target.Execute() at NAnt.Core.Project.Execute(String targetName) at NAnt.Core.Project.Execute() at NAnt.Core.Project.Run() Please send bug report to [EMAIL PROTECTED] Philippe Lavoie Cactus Commerce eBusiness. All Business. Tel 819.778.0313 x302 * 888.CACTUS.0 * Fax 819.771.0921 www.cactuscommerce.com [EMAIL PROTECTED] -Original Message- From: Matthew Mastracci [mailto:[EMAIL PROTECTED] Sent: Thursday, July 03, 2003 12:07 PM To: Philippe Lavoie Cc: [EMAIL PROTECTED] Subject: Re: [nant-dev] Bug in solution task with a web project Is CSC.EXE in your path while running NAnt? I'm hoping one day to add a web path mapping property to the solution task. Right now it has a very basic set of error-prone WebDAV methods to handle compiling of a web project that is usually on the build server anyways. It also tries to use the credentials of the logged-in user. Microsoft uses the FrontPage extensions to work around these problems. It seems to work better with IIS. Philippe Lavoie wrote: I wanted to use slingshot and for some reason it would load (and it doesn't work with VS 2003 anyway). Then, I noticed that the solution might be the way to go. I added a simple solution task to my build system ?xml version=1.0? project name=App default=build property name=debug value=true/ property name=build.basedir value=Build / target name=build solution configuration=debug solutionfile=source/App.sln/ /target /project The first time I was getting a 403 error (the web project is a virtual directory which points back inside my source directory). Fixed that by adding a checkbox to every permission available inside that directory. Then I ran the script again and got Nant -debug http://localhost/AppWeb/FixedTermLoan/Product.aspx.vb http://localhost/AppWeb/FixedTermLoan/Product.aspx.resx [solution] Building APP [debug]... [solution] Copying references: [solution] - System [solution] - System.Data [solution] - Microsoft.ApplicationBlocks.Data [copy] Copying 0 files to C:\Projects\App-dev\Latest\source\L ibrary\APP\bin\. [solution] - System.XML [solution] Compiling resources: [solution] Starting compiler... Total time: 0 seconds. BUILD FAILED INTERNAL ERROR System.ComponentModel.Win32Exception: The system cannot find the file specified at System.Diagnostics.Process.StartWithCreateProcess(ProcessStartInfo startIn fo) at System.Diagnostics.Process.Start() at System.Diagnostics.Process.Start(ProcessStartInfo startInfo) at NAnt.VSNet.Tasks.Project.Compile(String strConfiguration, ArrayList alCSCA rguments, String strLogFile, Boolean bVerbose, Boolean bShowCommands) at NAnt.VSNet.Tasks.Solution.Compile(String strConfiguration, ArrayList alCSC Arguments, String strLogFile, Boolean bVerbose, Boolean bShowCommands) at NAnt.VSNet.Tasks.SolutionTask.ExecuteTask() at NAnt.Core.Task.Execute() at NAnt.Core.Target.Execute() at NAnt.Core.Project.Execute(String targetName) at NAnt.Core.Project.Execute() at NAnt.Core.Project.Run() Please send bug report to [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]. I'm using the latest snapshot available 20030621 (as the CVS source available from anonymous don't want to build. I'll send another report for that.) I wish I knew more what the problem was, since it seems I won't be able to use nant until this is fixed... Philippe Lavoie Cactus Commerce eBusiness. All Business. Tel 819.778.0313 x302 * 888.CACTUS.0 * Fax 819.771.0921 www.cactuscommerce.com [EMAIL PROTECTED] --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET.
Re: [nant-dev] Bug in solution task with a web project
Phillippe: I've checked in a fix that allows you to generate VB resources from the WinForms projects. As far as I can tell, it generates identical resource filenames to VS.NET's. I can send you a pre-compiled solution task if you'd like - it may work within your NAnt installation. Matthew Mastracci wrote: Someone posted a patch for this item earlier... I don't know if it was ever applied. I can look and make sure it's in CVS. Philippe Lavoie wrote: That did the trick, I added vbc (by contract, not choice) to the path and now it got a lot further. However, now it's stuck with the following which I hope is now fixed inside CVS (except that I can't compile CVS... ) Web_IClicWeb.vbproj\Global.asax.resx Total time: 0 seconds. BUILD FAILED INTERNAL ERROR System.ArgumentException: Can't parse VB files yet at NAnt.VSNet.Tasks.Resource.GetDependentResourceName(String strDependentFile ) at NAnt.VSNet.Tasks.Resource.CompileResx() at NAnt.VSNet.Tasks.Resource.Compile(ConfigurationSettings cs, Boolean bShowC ommands) at NAnt.VSNet.Tasks.Project.Compile(String strConfiguration, ArrayList alCSCA rguments, String strLogFile, Boolean bVerbose, Boolean bShowCommands) at NAnt.VSNet.Tasks.Solution.Compile(String strConfiguration, ArrayList alCSC Arguments, String strLogFile, Boolean bVerbose, Boolean bShowCommands) at NAnt.VSNet.Tasks.SolutionTask.ExecuteTask() at NAnt.Core.Task.Execute() at NAnt.Core.Target.Execute() at NAnt.Core.Project.Execute(String targetName) at NAnt.Core.Project.Execute() at NAnt.Core.Project.Run() Please send bug report to [EMAIL PROTECTED] Philippe Lavoie Cactus Commerce eBusiness. All Business. Tel 819.778.0313 x302 * 888.CACTUS.0 * Fax 819.771.0921 www.cactuscommerce.com [EMAIL PROTECTED] -Original Message- From: Matthew Mastracci [mailto:[EMAIL PROTECTED] Sent: Thursday, July 03, 2003 12:07 PM To: Philippe Lavoie Cc: [EMAIL PROTECTED] Subject: Re: [nant-dev] Bug in solution task with a web project Is CSC.EXE in your path while running NAnt? I'm hoping one day to add a web path mapping property to the solution task. Right now it has a very basic set of error-prone WebDAV methods to handle compiling of a web project that is usually on the build server anyways. It also tries to use the credentials of the logged-in user. Microsoft uses the FrontPage extensions to work around these problems. It seems to work better with IIS. Philippe Lavoie wrote: I wanted to use slingshot and for some reason it would load (and it doesn't work with VS 2003 anyway). Then, I noticed that the solution might be the way to go. I added a simple solution task to my build system ?xml version=1.0? project name=App default=build property name=debug value=true/ property name=build.basedir value=Build / target name=build solution configuration=debug solutionfile=source/App.sln/ /target /project The first time I was getting a 403 error (the web project is a virtual directory which points back inside my source directory). Fixed that by adding a checkbox to every permission available inside that directory. Then I ran the script again and got Nant -debug http://localhost/AppWeb/FixedTermLoan/Product.aspx.vb http://localhost/AppWeb/FixedTermLoan/Product.aspx.resx [solution] Building APP [debug]... [solution] Copying references: [solution] - System [solution] - System.Data [solution] - Microsoft.ApplicationBlocks.Data [copy] Copying 0 files to C:\Projects\App-dev\Latest\source\L ibrary\APP\bin\. [solution] - System.XML [solution] Compiling resources: [solution] Starting compiler... Total time: 0 seconds. BUILD FAILED INTERNAL ERROR System.ComponentModel.Win32Exception: The system cannot find the file specified at System.Diagnostics.Process.StartWithCreateProcess(ProcessStartInfo startIn fo) at System.Diagnostics.Process.Start() at System.Diagnostics.Process.Start(ProcessStartInfo startInfo) at NAnt.VSNet.Tasks.Project.Compile(String strConfiguration, ArrayList alCSCA rguments, String strLogFile, Boolean bVerbose, Boolean bShowCommands) at NAnt.VSNet.Tasks.Solution.Compile(String strConfiguration, ArrayList alCSC Arguments, String strLogFile, Boolean bVerbose, Boolean bShowCommands) at NAnt.VSNet.Tasks.SolutionTask.ExecuteTask() at NAnt.Core.Task.Execute() at NAnt.Core.Target.Execute() at NAnt.Core.Project.Execute(String targetName) at NAnt.Core.Project.Execute() at NAnt.Core.Project.Run() Please send bug report to [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]. I'm using the latest snapshot available 20030621 (as the CVS source available from anonymous don't want to build. I'll send another report for that.) I wish I knew more what the problem was, since it seems I won't be able to use nant until this is fixed... Philippe Lavoie Cactus Commerce eBusiness. All Business. Tel 819.778.0313 x302 * 888.CACTUS.0 * Fax 819.771.0921 www.cactuscommerce.com [EMAIL PROTECTED]
[nant-dev] NAntContrib branch for 0.8.3
Can someone with CVS write access create a branch for the upcoming 0.8.3 release? Ian says he has the project building and testing cleanly, so now is a good time to branch. The command is: cvs tag -b BRANCH-083 After running the command, you will still be on the main branch and people can start committing again. Please increment the version number on the main branch to 0.8.4. Release notes, bug fixes, et al will be checked into the branch and merged onto the main branch after the final release. There will be a release candidate of NAnt 0.8.3 this weekend, and NAntContrib will ship as part of it. Release notes will be submitted to the list for review before the release candidate ships. On a related note, I do have the tests building cleanly (and am thus happy to branch) but do not have all the tests passing. Ian, can you tell me how you got this to pass? 1) NAnt.Contrib.Tests.TlbImpTaskTest.Test_SanityCheck : The type initializer for NAnt.Core.Project threw an exception. at NAnt.Core.Project..ctor(String uriOrFilePath, Level threshold) at Tests.NAnt.Core.BuildTestBase.CreateFilebasedProject(String xml) at Tests.NAnt.Core.BuildTestBase.RunBuild(String xml) at NAnt.Contrib.Tests.TlbImpTaskTest.Test_SanityCheck() in c:\source\tools\NAntContrib\Tests\Tasks\TlbImpTaskTest.cs:line 51 John C Barstow --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0016ave/direct;at.asp_061203_01/01 ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
[nant-dev] Re: [NAntC-Dev] NAnt.Optional.zip
Hi Ian, I send you both files for the record task. Just tested them with latest version of NAnt and NAntContrib from cvs and they compile and works. It should find them there. Are you running nant from \build\nant-0.8.3-debug\bin and does the nant.exe.config in that directory contain : nantsettings defaultframework=net-1.0 taskpath=.\optional taskpath allows you specify a ';' seperated list of directories that contain task assemblies. You may need to cvs update nant as well to get the taskpath related changes. That was it... I was running with the latest nightly build, since i can get code from cvs at work, where i tested it. Just a question, why if the task path a ';' separated list and not simply child nodes of nantsettings, with a node for each directory ? Nick From: Ian MacLean [EMAIL PROTECTED] To: [EMAIL PROTECTED] CC: 'N. V.' [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Re: [NAntC-Dev] NAnt.Optional.zip Date: Thu, 03 Jul 2003 17:14:15 +0900 MIME-Version: 1.0 sorry for the confusion but : we decided to keep the tasks in NAntcontrib for now and move a bunch of them into nant - post 0.83 release - see the 'Namespaces and NAnt.Cnntrib tasks' post for details on what tasks will go where. but don't worry the bullet remains bitten. I've rolled the changes that are in NAnt.optional.zip back into nantcontrib which is now building against current NAnt cvs. We will ship a nant contrib task assembly with nant for the upcoming release. Nick: But the record task doesn't work, it simply create an empty file and doesn't loag anything into it. Since I have an updated version, which works with the new logging system, i could sent it to you, after making some minors changes to reflect the namespace changes. that would be awesome. All I did was comment stuff until it compiled. If you have a version that works with the new logging system just send it to me and I'll commit. Another thing, I had to move the dll's from the bin\optional directly into bin to have NAnt recognize the tasks. It should find them there. Are you running nant from \build\nant-0.8.3-debug\bin and does the nant.exe.config in that directory contain : nantsettings defaultframework=net-1.0 taskpath=.\optional taskpath allows you specify a ';' seperated list of directories that contain task assemblies. You may need to cvs update nant as well to get the taskpath related changes. Ian further 2 cents: 1) thanks for biting the bullet, very much! 2) does it make sense that nantcontrib ends up in a single dll as opposed to several dlls, smaller, per task set? seems to me it might complicate the configuration a little bit more, but would yield easier to handle subproject (eg: if one task is broken, the whole thing isn't broken...) /jean -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of N. V. Sent: Wednesday, July 02, 2003 17:37 To: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: [NAntC-Dev] NAnt.Optional.zip Hi Ian, I just tested this, with my build files which uses vssget, sql and record task and the vssget and sql task works fines (i prefered when the sql task wasn't writting every params to the the Console, but that's not really a problem). Another thing, I had to move the dll's from the bin\optional directly into bin to have NAnt recognize the tasks. Nick From: Ian MacLean [EMAIL PROTECTED] To: [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: [NAntC-Dev] NAnt.Optional.zip Date: Sun, 29 Jun 2003 20:08:22 +0900 grab it from http://www26.brinkster.com/ianm74/NAnt.Optional.zip unzip it under nant\src and add the following line to TaskAssemblies.txt : NAnt.Optional then just run the main nant build. this creates a new folder optional under build\nant-0.8.3-debug\bin with the optional tasks dll and its dependencies. If you run the newly built NAnt it will load the optional tasks as well as the core ones. I just got it compiling and tested a few of the tasks. Please try it out and let me know if anything is broken. Ian _ MSN Messenger : discutez en direct avec vos amis ! http://messenger.fr.msn.ca/ // // NAntContrib // Copyright (C) 2002 Tomas Restrepo ([EMAIL PROTECTED]) // // This library is free software; you can redistribute it and/or // modify it under the terms of the GNU Lesser General Public // License as published by the Free Software Foundation; either // version 2.1 of the License, or (at your option) any later version. // // This library is distributed in the hope that it will be useful, // but WITHOUT ANY WARRANTY; without even the implied warranty of // MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU // Lesser General Public License for more details. // // You should have received a copy of the GNU Lesser General Public // License along with this library; if not, write to the Free
[nant-dev] Re: NAntContrib branch for 0.8.3
John Barstow wrote: On a related note, I do have the tests building cleanly (and am thus happy to branch) but do not have all the tests passing. Ian, can you tell me how you got this to pass? did you sync NAntCOntrib.build ? TlbImpTask has a dependency on DotnetTasks.dll which wasn't being copied to the NAntContrib build directory. we need to get the error propagation a bit better so that the test failures are a bit more informative than The type initializer for NAnt.Core.Project threw an exception. Having to track them down in the debugger is bit of a pain. Ian 1) NAnt.Contrib.Tests.TlbImpTaskTest.Test_SanityCheck : The type initializer for NAnt.Core.Project threw an exception. at NAnt.Core.Project..ctor(String uriOrFilePath, Level threshold) at Tests.NAnt.Core.BuildTestBase.CreateFilebasedProject(String xml) at Tests.NAnt.Core.BuildTestBase.RunBuild(String xml) at NAnt.Contrib.Tests.TlbImpTaskTest.Test_SanityCheck() in c:\source\tools\NAntContrib\Tests\Tasks\TlbImpTaskTest.cs:line 51 John C Barstow --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0016ave/direct;at.asp_061203_01/01 ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
[nant-dev] Re: [NAntC-Dev] NAnt.Optional.zip
Nick I send you both files for the record task. Just tested them with latest version of NAnt and NAntContrib from cvs and they compile and works. committed. Please be aware of the whitespace and formatting standards for nant - http://sourceforge.net/docman/display_doc.php?docid=6080group_id=31650 otherwise its good. Thanks. Just a question, why if the task path a ';' separated list and not simply child nodes of nantsettings, with a node for each directory ? technically a ; seperated string is simpler than a set of child nodes. I'm not too bothered either way. There is a strong precedent for ; seperated paths - but a node for each directory is more explicit. Ian Nick From: Ian MacLean [EMAIL PROTECTED] To: [EMAIL PROTECTED] CC: 'N. V.' [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Re: [NAntC-Dev] NAnt.Optional.zip Date: Thu, 03 Jul 2003 17:14:15 +0900 MIME-Version: 1.0 sorry for the confusion but : we decided to keep the tasks in NAntcontrib for now and move a bunch of them into nant - post 0.83 release - see the 'Namespaces and NAnt.Cnntrib tasks' post for details on what tasks will go where. but don't worry the bullet remains bitten. I've rolled the changes that are in NAnt.optional.zip back into nantcontrib which is now building against current NAnt cvs. We will ship a nant contrib task assembly with nant for the upcoming release. Nick: But the record task doesn't work, it simply create an empty file and doesn't loag anything into it. Since I have an updated version, which works with the new logging system, i could sent it to you, after making some minors changes to reflect the namespace changes. that would be awesome. All I did was comment stuff until it compiled. If you have a version that works with the new logging system just send it to me and I'll commit. Another thing, I had to move the dll's from the bin\optional directly into bin to have NAnt recognize the tasks. It should find them there. Are you running nant from \build\nant-0.8.3-debug\bin and does the nant.exe.config in that directory contain : nantsettings defaultframework=net-1.0 taskpath=.\optional taskpath allows you specify a ';' seperated list of directories that contain task assemblies. You may need to cvs update nant as well to get the taskpath related changes. Ian further 2 cents: 1) thanks for biting the bullet, very much! 2) does it make sense that nantcontrib ends up in a single dll as opposed to several dlls, smaller, per task set? seems to me it might complicate the configuration a little bit more, but would yield easier to handle subproject (eg: if one task is broken, the whole thing isn't broken...) /jean --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0016ave/direct;at.asp_061203_01/01 ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
RE: [nant-dev] onsuccess / failure
Hello, To be consistent, this would be a useful change. Maybe NAnt should output a warning if the nant.failure task is still found after this change. Best regards, Bernard -Original Message- From: Gert Driesen [mailto:[EMAIL PROTECTED] Sent: Thursday, July 03, 2003 8:29 AM To: Nant-Developers (E-Mail) Subject: [nant-dev] onsuccess / failure Hi, Is it ok to rename the properties that designates a target to execute when the build fails from nant.failure to nant.onfailure, to have it in sync with nant.onsuccess ? I know this is a breaking change, so we should document it as such in the release notes. In my opinion, changes like these should still be allowed, as long as they're clearly documented. Gert --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0016ave/direct;at.asp_061203_01/01 ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0016ave/direct;at.asp_061203_01/01 ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
Re: [nant-dev] onsuccess / failure
It will output a warning if it's still used, and will continue to actually use it for now. - Original Message - From: Bernard Vander Beken [EMAIL PROTECTED] To: Gert Driesen [EMAIL PROTECTED]; Nant-Developers (E-Mail) [EMAIL PROTECTED] Sent: Thursday, July 03, 2003 8:45 AM Subject: RE: [nant-dev] onsuccess / failure Hello, To be consistent, this would be a useful change. Maybe NAnt should output a warning if the nant.failure task is still found after this change. Best regards, Bernard -Original Message- From: Gert Driesen [mailto:[EMAIL PROTECTED] Sent: Thursday, July 03, 2003 8:29 AM To: Nant-Developers (E-Mail) Subject: [nant-dev] onsuccess / failure Hi, Is it ok to rename the properties that designates a target to execute when the build fails from nant.failure to nant.onfailure, to have it in sync with nant.onsuccess ? I know this is a breaking change, so we should document it as such in the release notes. In my opinion, changes like these should still be allowed, as long as they're clearly documented. Gert --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0016ave/direct;at.asp_061203_01/01 ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0016ave/direct;at.asp_061203_01/01 ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0016ave/direct;at.asp_061203_01/01 ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
[nant-dev] RE: [NAntC-Dev] NAnt.Optional.zip
further 2 cents: 1) thanks for biting the bullet, very much! 2) does it make sense that nantcontrib ends up in a single dll as opposed to several dlls, smaller, per task set? seems to me it might complicate the configuration a little bit more, but would yield easier to handle subproject (eg: if one task is broken, the whole thing isn't broken...) /jean -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of N. V. Sent: Wednesday, July 02, 2003 17:37 To: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: [NAntC-Dev] NAnt.Optional.zip Hi Ian, I just tested this, with my build files which uses vssget, sql and record task and the vssget and sql task works fines (i prefered when the sql task wasn't writting every params to the the Console, but that's not really a problem). But the record task doesn't work, it simply create an empty file and doesn't loag anything into it. Since I have an updated version, which works with the new logging system, i could sent it to you, after making some minors changes to reflect the namespace changes. Another thing, I had to move the dll's from the bin\optional directly into bin to have NAnt recognize the tasks. Nick From: Ian MacLean [EMAIL PROTECTED] To: [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: [NAntC-Dev] NAnt.Optional.zip Date: Sun, 29 Jun 2003 20:08:22 +0900 grab it from http://www26.brinkster.com/ianm74/NAnt.Optional.zip unzip it under nant\src and add the following line to TaskAssemblies.txt : NAnt.Optional then just run the main nant build. this creates a new folder optional under build\nant-0.8.3-debug\bin with the optional tasks dll and its dependencies. If you run the newly built NAnt it will load the optional tasks as well as the core ones. I just got it compiling and tested a few of the tasks. Please try it out and let me know if anything is broken. Ian --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0016ave/direct;at.asp_0 61203_01/0 1 ___ NAntContrib-Developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nantcontrib-developer _ MSN Messenger : discutez en direct avec vos amis ! http://messenger.fr.msn.ca/ --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0016ave/direct;at.asp_06 1203_01/01 ___ NAntContrib-Developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nantcontrib-developer --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0016ave/direct;at.asp_061203_01/01 ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
[nant-dev] RE: [Nant-users] LONG: New idea for handling build configurations
I think you are on to something here. I only use NAnt right now to build
release candidate code so don't have the need for multi configuration
builds, but your idea is certainly good.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Jaroslaw
Kowalski
Sent: Saturday, June 28, 2003 06:16
To: [EMAIL PROTECTED]
Cc: NAnt Developers
Subject: [Nant-users] LONG: New idea for handling build configurations
Hi all!
Recently Giuseppe has prepared a document that describes recommended build
configurations. This document and c.a. 99.441% of all build files in the
universe attempt to invent their own methods for setting up parameters like:
debug, optimize, defines for master and child builds.
THE PROBLEM:
Most of the time you see this:
property name=something.debug value=... /
property name=something.optimize value=... /
and then
csc ... debug=${something.debug} optimize=${something.optimize}
/csc
and all csc tasks tend to use the same settings in the whole buildfile.
I think that the following covers at least 80% of all cases:
1. Most of the build files are simple: they use a single setting for
debug, optimize, defines in all their outputs.
2. Builds that have many subdirectories tend to pass their current settings
to sub-builds (we have inheritance here).
3. Most of the time you want to have configurations like: debug and
release configurations (perhaps something third, but nothing more).
4. Build files tend to produce their output to a single directory, because
it's in accordance to .NET deployment model, so being able to specify a
default target directory makes sense in general.
5. You need to write some boilerplate code even for the simplest tasks if
you want any degree of flexibility
THE SOLUTION - IDEA
===
My idea (not complete yet, but may serve as a base for some discussion) is
to introduce a concept of configurations.
The configuration would define and group the most commonly used settings
(perhaps global properties) like:
default value of debug parameter for all tasks
default value of optimize parameter for all tasks
default value of defines parameter for all tasks
default value for output directory for all tasks
(and perhaps even more reasonable defaults)
You would invoke NAnt by specifying the build file and the configuration
(both can have defaults specified in project tag.
NAnt.exe -cfg:debug build
would build target build with configuration debug.
It would be possible to build all configurations by something like
NAnt.exe -cfg:all build
The configuration definition would be provided by:
NAnt:
NAnt would provide reasonable defaults for flags like debug,
optimize,
defines, and output directory. They should be provided (perhaps in
NAnt.exe.config)
for debug and release configurations.
command line:
Users may want to override some particular setting on the command line
nant.exe -D:default.csc.debug=false
configuration file:
(not well thought out, but I think it sould be
possible so you don't need to specify long command lines)
build file:
Build file would contain a bunch of:
configuration name=debug
property name=default.jsc.debug value=false /
property name=default.csc.debug value=true /
property name=default.debug value=true /
property name=default.csc.outdir value=bin/debug /
/configuration
configuration name=release
property name=default.jsc.debug value=false /
property name=default.csc.debug value=true /
property name=default.debug value=true /
property name=default.csc.outdir value=bin/release /
/configuration
As you can see I propose some form of default values inheritance. For
example csc task whould look for the value for its debug parameter by
looking at (in order):
- the value specified in csc task
- if it's not found, get it from default.csc.debug
- if it's not specified, get the value from default.debug
And all csc tasks would be reduced to:
csc target=winexe output=test.exe
sources
/sources
/csc
instead of (ugly in my opinion):
csc
target=winexe
output=${something.outdir}/test.exe
debug=${something.debug}
optimize=${something.optimize}
define=${something.define}
sources
/sources
...
/csc
The idea is to have ultra-clean, yet very flexible build files that would be
very easy to create and maintain.
I think it would be simple to implement it using current model of
properties.
What do you think?
Jarek
---
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa0016ave/direct;at.asp_061203_01/01
___
Nant-users mailing list
[EMAIL PROTECTED]
