[nant-dev] [ANN] Nant 0.8.3-RC2 released
RC2 of the 0.8.3 release is now available for download at http://sourceforge.net/project/showfiles.php?group_id=31650release_id=17472 5 Text version of changes since RC1: USER-VISIBLE CHANGES * Built with .NET 1.0 This release candidate is built with version 1.0 of the .NET Framework. The binaries for RC1 had been built with version 1.1, which had backwards compatibility issues. * Fixed defect: temp directory leak in solution task Matthew Mastracci fixed a major temp directory leak. It was leaking approx. one temp directory per project! You should clear your Local Settings\Temp directory for the user you use to build your solutions. * solution VB.NET support The solution task now supports VB.NET projects. This was meant to be part of the RC1 release. * Matthew Mastracci has also checked in support for reading resources of VB projects and generating the appropriate dependent resource name. * Documentation for NAntContrib This release candidate includes the binaries and documentation for the NAntContrib extensions. Note that the source is still distributed seperately during this release cycle. John C Barstow 0.8.3 Release Manager P.S. A project admin may want to create a SF news item. --- 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/psa0013ave/direct;at.aspnet_072303_01/01 ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
RE: [nant-dev] [0.8.3] RC2 build failure
Apparently you've committed the NAnt.VSNet.build from the main branch to the 0.8.3 branch. No problem, I've got the build happening. I'll commit my changes back to the branch before tagging the release. Barring any unexpected issues, RC2 will be out tonight. 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/psa0013ave/direct;at.aspnet_072303_01/01 ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
[nant-dev] [0.8.3] RC2 buld failures
I'm getting the following build failure when attempting to build NAntContrib on the 0.8.3 branch with the 1.0 NET framework. I'd like to fix it before shipping RC2. Any ideas? compile.schemas: [loadtasks] Loading tasks from assembly C:\source\tools\NAntContrib/build/nantcontrib-0 .1.0.0-debug\NAnt.Xsd.Tasks.dll. [xsd] Compiling Schema src\Tasks\MSITask.xsd into Microsoft.NET classes [xsd] Starting 'C:\Program Files\Microsoft.NET\SDK\v1.1\bin\xsd.exe (/nologo src\ Tasks\MSITask.xsd /classes /l:CS /n:NAnt.Contrib.Schemas.MSI /o:C:\source\tools\NAntCon trib/build/nantcontrib-0.1.0.0-debug\Schemas\MSI /u:NAnt.Contrib.Tasks.MSITask)' in 'C: \source\tools\NAntContrib' Writing file 'C:\source\tools\NAntContrib/build/nantcontrib-0.1.0.0-debug\S chemas\MSI\MSITask.cs'. Total time: 16 seconds. BUILD FAILED INTERNAL ERROR System.Security.SecurityException: Request for the permission of type System.Security.P ermissions.StrongNameIdentityPermission, mscorlib, Version=1.0.3300.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 failed. at System.Xml.XmlTextReader..ctor(String url, XmlNameTable nt) at System.Xml.XmlDocument.Load(String filename) at NAnt.Contrib.Tasks.XsdTask.ExecuteTask() at NAnt.Core.Task.Execute() at NAnt.Core.TaskContainer.ExecuteChildTasks() at NAnt.Core.Tasks.IfTask.ExecuteTask() at NAnt.Core.Task.Execute() at NAnt.Core.Target.Execute() at NAnt.Core.Target.Execute() at NAnt.Core.Project.Execute(String targetName) at NAnt.Core.Project.Execute() at NAnt.Core.Project.Run() The state of the failed permission was: IPermission class=System.Security.Permissions.StrongNameIdentityPermission, mscorlib, Version=1.0.3300.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 version=1 PublicKeyBlob=0400 Name=System.Windows.Forms/ 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/psa0013ave/direct;at.aspnet_072303_01/01 ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
[nant-dev] [0.8.3] RC2 build failure
I'm doing the build of RC2 with the 1.0 Framework and getting the following build failure. I assume it's related to the check-ins for the solution fixes. This is on BRANCH-083. BUILD FAILED C:\source\tools\nant\src\NAnt.VSNet\NAnt.VSNet.build(11,10): Property 'current.build.defines' has not been set! 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/psa0013ave/direct;at.aspnet_072303_01/01 ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
[nant-dev] Delay in RC1a
I apologize for the delay in re-releasing RC1 as built with the 1.0 framework. The network admin gave away the machine I had with 1.0 installed on it, so I have been scrambling for a machine with the 1.0 framework installed. I have located such a machine, and am in the process of configuring it. Hopefully there will be a release tomorrow. If there are no other major issues, we will release the final version around 23-July. People who have the framework 1.1 version installed can report bugs with RC1. Please put RC1 in the subject line somewhere to ensure I see the report. The re-release will have a new revision number and be released as RC1a. There is no plan to have new code, although there may be some clarifications in the release notes. There *will* be an announcement this time; kept it quiet last time because the 1.1 issue was identified almost immediately. John C Barstow --- This SF.net email is sponsored by: VM Ware With VMware you can run multiple operating systems on a single machine. WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the same time. Free trial click here: http://www.vmware.com/wl/offer/345/0 ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
RE: [nant-dev] Nant 0.8.3 rc1 and framework 1.0 problem
I will prop a version built with the 1.0 framework today. My fault entirely; since I wasn't getting errors in my tests I assumed everything was fine. John C Barstow -Original Message- From: N. V. [mailto:[EMAIL PROTECTED] Sent: Tuesday, 15 July 2003 12:05 a.m. To: [EMAIL PROTECTED] Subject: [nant-dev] Nant 0.8.3 rc1 and framework 1.0 problem Hi, Using the 0.8.3 rc1. NAnt refuse to start on a computer having only the 1.0 framework, giving the following error message: .NET Framework initialization error: C:\WinNT\Framework\v1.1.4322\mscorwks.dll could not be loaded. Nick _ MSN Messenger : discutez en direct avec vos amis ! http://messenger.fr.msn.ca/ --- This SF.Net email sponsored by: Parasoft Error proof Web apps, automate testing more. Download eval WebKing and get a free book. www.parasoft.com/bulletproofapps1 ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers --- This SF.Net email sponsored by: Parasoft Error proof Web apps, automate testing more. Download eval WebKing and get a free book. www.parasoft.com/bulletproofapps1 ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
[nant-dev] RE: NAnt version number
Gert Driesen [mailto:[EMAIL PROTECTED] wrote: I'm not sure about this, but wasn't it the intention to using the following version numbering scheme : major.minor.revision.YMMDD eg. 0.8.3.30710 (if a release would be built today) ? Or do you have another proposal ? I will be recording the RC and release revision numbers going forward, whatever they are. I don't think that we had settled on a format for the build number, just that we would increment and track the build number. I somewhat randomly picked 5 for the RC1 branch, but haven't uploaded the tarball yet. My proposal is that nightly builds should have a build number of the format: 0.8.3.YYMMDD That way it's always clear that this is, in fact, a development build. We should be able to add this to the daily build script to auto-increment. Release candidates and releases should have the format: 0.8.3.xx, where xx is a number that increments for every release candidate. So RC1 would be 0.8.3.01, RC2 would be 0.8.3.02, etc. That way it's clear that this is, in fact, an officially released build and is simple to note. The release manager just needs to pass in the version number on the command line. It's trivial for me to reroll the tarball if needed. I don't know what to do with CVS builds. Subversion has nice global revision numbers, but I have no idea what to do without those. Maybe we just use the date scheme. Should we also output the NAnt revision number when launching NAnt ? Yes, I think so. People usually use that number for reporting bugs. John C Barstow --- This SF.Net email sponsored by: Parasoft Error proof Web apps, automate testing more. Download eval WebKing and get a free book. www.parasoft.com/bulletproofapps1 ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
RE: [nant-dev] For review - 0.8.3 rc1 release notes
I've incorporated everyone's comments and am rolling the tarball now. Thanks for the feedback. John C Barstow --- This SF.Net email sponsored by: Parasoft Error proof Web apps, automate testing more. Download eval WebKing and get a free book. www.parasoft.com/bulletproofapps1 ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
[nant-dev] For review - 0.8.3 rc1 release notes
0.8.3rc1 release notes (plain text format)
Please review and post your comments to the mailing list. I'm starting the
release process tonight with the 0.8.3 branch. It's a bit more detailed than
previous logs, but I think I got all the significant changes that might
impact an unwary user.
John C Barstow
USER-VISIBLE CHANGES
- NAntContrib is now distributed with NAnt.
To better support the frequently-used NAntContrib extensions, the library
is now distributed as part of the NAnt release.
- Preliminary Linux support with Mono 0.25.
This is the first release with Linux support, so please report any issues
you encounter. The next release will be fully tested and documented on boht
Linux and Windows.
- New Tasks
See the user documentation for usage details.
) cvs: Performs various CVS tasks.
) cvs-checkout: Checkout source from CVS.
) cvs-update: Update source from CVS.
) mcs: Compile using the mono compiler. Note that the functionality of
this task will be likely be incorporated into the csc task.
) solution: compile .sln directly. In most cases, this means you no
longer have to preprocess a solution with the slingshot tool.
- Changed Tasks
See the section below for details.
- Fileset References
You can now define a named fileset and refer to it anywhere a fileset is
used.
DEVELOPER-VISIBLE CHANGES
- Namespace changes
There have been major code reorganizations since the last release.
) SourceForge is no longer part of the NAnt namespaces.
) Split classes up into Tasks and Types.
) Task assemblies now have their own namespaces.
) Removed Msft prefix from base classes.
- Logging framework changed. The logging framework is now based on
Log4Net.
) Refactored NAnt (build) logging system : moved to an event driver
logging system, and allow thresholds to be set. The build outcome is now
completely handled by the loggers.
) Replaced the LogListener with an IBuildLogger interface for loggers
and an IBuildListener interface for build listeners.
) The ConsoleLogger is replaced by a DefaultLogger, which always logs to
the console, and which can also be configured to log to a file (using the
-logfile option).
) The static Log class is removed and replaced by instance methods on
the Project and Task classes. These instance methods actually fire events
that get handled by the build logger and buid listeners.
) Added a Level enum that is used to assign a priority (level) to a
message. This allows messages to be filtered on their priority.
) Added a strongly typed collection for the build listeners.
) Updated all existing logging statements to use the new logging system
instead of the static Log class. Assigned levels to the existing logging
statements.
) Added MailLogger that can be used to send the build results as an
email, see xml docs for how its to be configured
- Many, many style/structure/documentation fixes. More that are worth
listing here.
- Fixed NUnit2 support for filesets.
- Prevent warnings for using obsolete methods to allow NDoc Document.Nant
to build on .NET 1.1 runtime.
- Nightly.xml No longer depends on NAntContrib tasks.
- Moved mail task and test back into core as its working fine on linux
now.
- New attribute-driven command-line parser.
SLINGSHOT CHANGES
- Fixed defect: slingshot now handles the fact that sln/proj files might
have a disparate list of configurations.
- Fixed defect: if a configuration name contains whitespace, it is
referenced in the slingshot output .build file w/ hyphens replacing
whitespace, as nant can't deal w/ blanks in target names.
- Added flexibility: the Clean.* targets are generated from the existing
list of configurations, in addition to the only hardcoded DebugClean and
ReleaseClean targets.
- Fixed limitation around references: references that are set to Copy
Local=true get copied to the build directory before compilation. otherwise,
the reference paths are explicitly listed in referencesincludes.
- New parameter: (per a suggestion from a user who replied to my notice of
impending changes) starting slingshot with the parameter replacerefs=...
triggers the reference paths to be replaced with the name of the build
configuration. for example, if projB references
d:\proj\projA\bin\Debug\projA.dll, when you slingshot projB with parameter
replacerefs=Debug, the reference to projA will look like
d:\proj\projA\bin\${slingshot.config}\projA.dll. when you then build
projB.build for config Release, the projA reference will look like this:
d:\proj\projA\bin\Release\projA.dll.
- Added support for WarningLevel (now that it's available in nant)
COMMAND-LINE CLIENT CHANGES
- Changed target back to the default argument.
- Moved company information (http://nant.sourceforge.net) from help text
to logo banner
- Added support for running default.build if
[nant-dev] pending 0.8.3 release candidate
Sorry to not have done any updates this weekend; I was dealing with a small emergency at work. I will circulate the change log tonight for review and package up the release candidate tomorrow. 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] 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] Branch for 0.8.3.xxx release
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
RE: [nant-dev] NAntContrib tests do not build
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
RE: [nant-dev] Nant.VisualCpp.Tasks build failures
The reason the unit tests were failing was because the INCLUDE and LIB environment variables were not set. We should add assertion checks for these environment variables in the unit tests so that a useful test failure message is generated. I have a TODO for myself, but it's a bite-sized task for someone who wants to contribute. Having fixed that, we now have a clean build of nant on a 1-1 framework machine. If anyone can verify the build on a 1-0 machine and on a mixed machine, we will be in a good place to release. I'm a little fuzzy on CVS (I use subversion for most of my work). Can we create a 0.8.3 release branch? If we do, we can restrict checkins on the branch to bug/doc/release note changes and everyone else can go on their way. If a branch would cause too much overhead, I think we should restrict checkins until the release which *should* be the end of this week. If the release date slips, I would argue for a branch so we don't build up a big backlog. 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] NAntContrib tests do not build
The NantContrib assemblies build just fine with the candidate 0.8.3, but the unit tests for NAntContrib fail to build. I expect to stage a release candidate in the next day or two, provided I can get the release notes written up and the majority of the NAntContrib unit tests passing in that timeframe. I will also do some ad hoc testing before then. 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
RE: [nant-dev] Nant.VisualCpp.Tasks build failures
Gert Driesen [mailto:[EMAIL PROTECTED] wrote: Do you have VS.NET installed ? The cpp compiler and stuff are not part of the .NET Framework. Is the C:\program Files\Microsoft Visual Studio .NET 2003\Vc7\bin directory in your path ? Surprisingly, the cpp compiler *is* part of .NET framework. However the compiler that is included may not be fully functional; which might be causing the error. The required directory is in the path. Currently there's no multiple framework support for the cpp tasks, as this is not possible with the current framework implementation which means the cpp linker and stuff have to be in your path right now. I've got a batch of changes ready that wil allow us to do that, but I'll hold off on them until after you've created a new release. Can you send me your changes privately or test them on a 1.1 machine? If they enable the test suite to pass without breaking the other unit tests, I'd recommend they go in as part of this release. Otherwise, we should write up a release note that explains how to make this task work correctly with multiple frameworks. Obviously, this highlights the need for me to have a 1.0-only machine set up. I'll try to make that happen this week. The actual error seems to be External Program Failed: cl (return code was 2), so it might not be a path issue after all, not sure about this one ... Sorry, I meant the error the compiler was returning. If I could run the failing build file by hand, I might be able to track the problem down and write a release note for it. 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
RE: [nant-dev] Fileset references
I forgot to make the filest in zip task settable - shold be fixed now. You added a unit test for this before fixing it, right? :) 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
RE: [nant-dev] NAntContrib
For what it's worth, here's my opinion. I'm trying to arrange things so releases will be less chaotic affairs, so that's my main bias in my arguments. NAntContrib should be distributed with NAnt. That means when we have a release, we build both and package all the binaries and source together. The list of tasks that make up NAnt need to stabilize before 1.0. There's too much change between releases (though more frequent releases will help fix this). By necessity, everything else needs to go into NAntContrib. I think for the next release (0.8.3.xxx), we should NOT restructure the code; it will only delay things and confuse people. Instead, we simply need to fix the project so it builds against the current version of NAnt. Both projects will be built and distributed together for this release. The following release (0.8.4.xxx), we should do whatever restructuring is necessary, as long as we can agree that no major refactorings are going to take place after this. One of the reasons my company is paying for me to work on this is because we are using the project in our production environment; if things start breaking I know I'm the one they're going to blame. After that (0.8.xxx), there needs to be a major push to test everything. Writing lots of test scripts, and a lot more unit tests. There are a number of subtle, untracked bugs caused by dependencies, cascades, etc. Part of the reason people complain about the extent of changes is so much stuff breaks. Better unit tests would make it a lot easier to find *and document* the scope of proposed changes before they are made. For the (0.9.xxx) releases, we really should be concentrating on documenting things and bug fixing. We need a *lot* more examples, so people don't keep reinventing the wheel and so people get a deep understanding of how build scripts work. Unfortunately, the major features that get implemented between releases make it much harder to get a deep understanding of the system; that makes it harder to contribute to the core and everyone ends up trying to commit to NAntContrib where everything breaks anyhow. I know there are lots of really useful features that need to be added, but the tasks that are in there TODAY are letting people write sophisticated, production-quality build systems. If we can polish and document the existing functionality, we have a solid core for a 1.0 release, and a much better foundation for integrating changes and tasks going forward. - As for doing my part, I am going to be writing some fairly extensive release notes this go round. Expect a first draft in about two days. In addition, I'm going to be putting in some more unit tests as soon as we ship 0.8.3.xxx. I'm also going to be pretty aggressive about trying to get out a new release every month. - 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] Unit test faliures
After some investigation, it looks like the unit tests are failing ONLY when run by the NAnt build file. Running the tests with nunit-console or nunit-gui results in the unit tests passing. To reproduce, do a clean checkout of the source, change to the newly created nant directory, and run bin\NAnt.exe. I'll do some more hacking on this over the weekend. One thing that struck me is that the original exception is not propogated; shouldn't unit tests be reporting the real, original exception instead of throwing a not-very-informative TestBuildException in its place? As a reminder, the failures are listed below. Buildfile: file:///C:/source/tools/nant/tests/NAnt.DotNet/NAnt.DotNet.build build: test: Tests run: 10, Failures: 6, Not run: 0, Time: 2.0937232 seconds Failures: 1) Tests.NAnt.DotNet.Tasks.CscTaskTest.Test_DebugBuild : Error Executing Project at Tests.NAnt.Core.BuildTestBase.ExecuteProject(Project p) in c:\source\tools\nant\tests\NAnt.Core\BuildTestBase.cs:line 96 at Tests.NAnt.Core.BuildTestBase.RunBuild(String xml) in c:\source\tools\nant\tests\NAnt.Core\BuildTestBase.cs:line 80 at Tests.NAnt.DotNet.Tasks.CscTaskTest.Test_DebugBuild() in c:\source\tools\nant\tests\NAnt.DotNet\Tasks\CscTaskTest.cs:line 64 2) Tests.NAnt.DotNet.Tasks.CscTaskTest.Test_ReleaseBuild : Error Executing Project at Tests.NAnt.Core.BuildTestBase.ExecuteProject(Project p) in c:\source\tools\nant\tests\NAnt.Core\BuildTestBase.cs:line 96 at Tests.NAnt.Core.BuildTestBase.RunBuild(String xml) in c:\source\tools\nant\tests\NAnt.Core\BuildTestBase.cs:line 80 at Tests.NAnt.DotNet.Tasks.CscTaskTest.Test_ReleaseBuild() in c:\source\tools\nant\tests\NAnt.DotNet\Tasks\CscTaskTest.cs:line 72 3) Tests.NAnt.DotNet.Tasks.JscTaskTest.Test_DebugBuild : Error Executing Project at Tests.NAnt.Core.BuildTestBase.ExecuteProject(Project p) in c:\source\tools\nant\tests\NAnt.Core\BuildTestBase.cs:line 96 at Tests.NAnt.Core.BuildTestBase.RunBuild(String xml) in c:\source\tools\nant\tests\NAnt.Core\BuildTestBase.cs:line 80 at Tests.NAnt.DotNet.Tasks.JscTaskTest.Test_DebugBuild() in c:\source\tools\nant\tests\NAnt.DotNet\Tasks\JscTaskTest.cs:line 58 4) Tests.NAnt.DotNet.Tasks.JscTaskTest.Test_ReleaseBuild : Error Executing Project at Tests.NAnt.Core.BuildTestBase.ExecuteProject(Project p) in c:\source\tools\nant\tests\NAnt.Core\BuildTestBase.cs:line 96 at Tests.NAnt.Core.BuildTestBase.RunBuild(String xml) in c:\source\tools\nant\tests\NAnt.Core\BuildTestBase.cs:line 80 at Tests.NAnt.DotNet.Tasks.JscTaskTest.Test_ReleaseBuild() in c:\source\tools\nant\tests\NAnt.DotNet\Tasks\JscTaskTest.cs:line 66 5) Tests.NAnt.DotNet.Tasks.VbcTaskTest.Test_DebugBuild : Error Executing Project at Tests.NAnt.Core.BuildTestBase.ExecuteProject(Project p) in c:\source\tools\nant\tests\NAnt.Core\BuildTestBase.cs:line 96 at Tests.NAnt.Core.BuildTestBase.RunBuild(String xml) in c:\source\tools\nant\tests\NAnt.Core\BuildTestBase.cs:line 80 at Tests.NAnt.DotNet.Tasks.VbcTaskTest.Test_DebugBuild() in c:\source\tools\nant\tests\NAnt.DotNet\Tasks\VbcTaskTest.cs:line 66 6) Tests.NAnt.DotNet.Tasks.VbcTaskTest.Test_ReleaseBuild : Error Executing Project at Tests.NAnt.Core.BuildTestBase.ExecuteProject(Project p) in c:\source\tools\nant\tests\NAnt.Core\BuildTestBase.cs:line 96 at Tests.NAnt.Core.BuildTestBase.RunBuild(String xml) in c:\source\tools\nant\tests\NAnt.Core\BuildTestBase.cs:line 80 at Tests.NAnt.DotNet.Tasks.VbcTaskTest.Test_ReleaseBuild() in c:\source\tools\nant\tests\NAnt.DotNet\Tasks\VbcTaskTest.cs:line 74 Total time: 3 seconds. BUILD FAILED --- This SF.Net email is sponsored by: INetU Attention Web Developers Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
RE: [nant-dev] Unit test faliures
After some investigation, it looks like the unit tests are failing ONLY when run by the NAnt build file. Running the tests with nunit-console or nunit-gui results in the unit tests passing. To reproduce, do a clean checkout of the source, change to the newly created nant directory, and run bin\NAnt.exe. I'll do some more hacking on this over the weekend. It appears to be related to the whole multiple framework issue. Specifically, I don't have 1.0 installed on my debugging machine, so the newly compiled nant.exe was unable to run anything. Since I was compiling with 1.1, this behavior is not really compliant with the side-by-side behavior dictated by MS. Odd that only the DotNet tests failed, though. There are four potential scenarios under Windows. 1) Only 1.0 installed. I cannot currently test this; may have something set up next week. 2) 1.0 and 1.1 side-by-side. I can snag a machine for this. 3) Only 1.1 installed. Our current default situation where I work. 4) Mono for Windows installed. I may be able to test this over the weekend; no promises. Thanks to side-by-side architecture, we're looking at the following interactions. a) Scenario 1, testing an assembly built using 1.1. This should work if the supportedRuntime is configured for the target assembly. b) Scenario 1, testing an assembly built using 1.0. Should be no problem at all. c) Scenario 1, testing an assembly built using Mono. Don't know what to expect. d) Scenario 3, testing an assembly built using 1.1. Should be no problem at all. e) Scenario 3, testing an assembly built using 1.0. This should work unless assembly specifically binds only to 1.0 framework. f) Scenario 3, testing an assembly built using Mono. Don't know what to expect. g) Scenario 2, testing an assembly built using 1.1. Should be no problem at all. h) Scenario 2, testing an assembly built using 1.0. Should be no problem at all. i) Scenario 2, testing an assembly built using Mono. Don't know what to expect. For g-i, behavior depends on supportedRuntime configuration for target assembly. j) Scenario 4, testing an assembly built using 1.1. Should be no problem at all, except for Mono bugs. k) Scenario 4, testing an assembly built using 1.0. Should be no problem at all, except for Mono bugs. l) Scenario 4, testing an assembly built using Mono. Should be no problem at all. Currently, there are issues with (d), (e), (g), and (h). This is because the default framework does not necessarily match what is installed on the machine, and because there are at least two versions of nant.exe that may be configured differently. Specifically, the bootstrap bin\nant.exe and the output nant.exe that is used for self-tests. I also don't know if (a) is tested. After reading through the MS notes, here's what I *think* should be happening. I'm still trying to locate the documentation for the nant config file so I understand all the issues. - We should default to the 1.1 framework if installed. - If not installed, we should default to the 1.0 framework. - We need to swap the order of the supportedRuntime tags so that the 1.1 framework is listed first. - If possible, we should examine the supportedRuntime of the target assembly. I think that having cases a,b,d,e,g,h working out of the box is a prerequisite for release. It'll take some testing, of course, but is necessary. (d) and(e) are especially key as service packs start forcing upgrades. Remember, if the target is compiled with the 1.1 framework it will run on 1.0 with the right config file. Finally, I would think it reasonable to require 1.1 to compile NAnt(the SDK is free, remember) as long as the resulting binary runs correctly under 1.0. I will be testing as many of these configurations over the weekend as possible. Worst case scenario I can fall back to testing and releasing only for scenarios (a) and (b). John C Barstow --- This SF.Net email is sponsored by: INetU Attention Web Developers Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
RE: Upcoming 0.8.4? release (was RE: [nant-dev] FW: Upcoming 0.8.3 release)
Erv Walter wrote: It seems kind of odd to suggest that the next version of NAnt should be 0.8.4, doesn't it? The newest release version is 0.8.2, why are we skipping 0.8.3? It's mainly because the CVS version has been marked as 0.8.3 for quite some time now, and it would be clearer to increment to 0.8.4 for a release. If support is not a concern, we can release it as 0.8.3. and let the chips fall where they may. N.V. wrote: Not everything built with framework 1.1 will work with framework 1.0, because a lot of thing have been added to framework 1.1, it's more like everything built with 1.0 will run with 1.1, and even then, i'm not sure There have been forward and backward breaking changes in 1.1. The fact is that the majority of assemblies are not affected; for those that are, the release notes document workarounds for the breaking changes. But the important thing is that we test any change like this before committing them. --- This SF.Net email is sponsored by: INetU Attention Web Developers Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
[nant-dev] RE: Upcoming 0.8.3 release
The following tests FAIL when attempting to build from the latest CVS. Sorry, I should mention the build environment is Windows XP running the net-1.1 framework. I will be installing Mandrake 9.1 with Mono 0.24 to test the linux builds. Tests results in other environments would be really helpful; I'll put together a list of 'known good' configurations for this release. -Original Message- From: John Barstow [mailto:[EMAIL PROTECTED] Sent: Thursday, 26 June 2003 5:15 p.m. To: Nant-Developers (E-mail) Subject: [nant-dev] FW: Upcoming 0.8.3 release I'm hoping to do an 0.8.3 release sometime next weekend. Before we can release, however, we'll need a clean build. The following tests FAIL when attempting to build from the latest CVS. If no-one fixes them before I wake up, I'll probably send in a patch or two. Note that they're ALL failing on the same line. (nant\tests\NAnt.Core\BuildTestBase.cs:line 96) Buildfile: file:///C:/source/tools/nant/tests/NAnt.DotNet/NAnt.DotNet.build build: test: Tests run: 10, Failures: 6, Not run: 0, Time: 2.0937232 seconds Failures: 1) Tests.NAnt.DotNet.Tasks.CscTaskTest.Test_DebugBuild : Error Executing Project at Tests.NAnt.Core.BuildTestBase.ExecuteProject(Project p) in c:\source\tools\nant\tests\NAnt.Core\BuildTestBase.cs:line 96 at Tests.NAnt.Core.BuildTestBase.RunBuild(String xml) in c:\source\tools\nant\tests\NAnt.Core\BuildTestBase.cs:line 80 at Tests.NAnt.DotNet.Tasks.CscTaskTest.Test_DebugBuild() in c:\source\tools\nant\tests\NAnt.DotNet\Tasks\CscTaskTest.cs:line 64 2) Tests.NAnt.DotNet.Tasks.CscTaskTest.Test_ReleaseBuild : Error Executing Project at Tests.NAnt.Core.BuildTestBase.ExecuteProject(Project p) in c:\source\tools\nant\tests\NAnt.Core\BuildTestBase.cs:line 96 at Tests.NAnt.Core.BuildTestBase.RunBuild(String xml) in c:\source\tools\nant\tests\NAnt.Core\BuildTestBase.cs:line 80 at Tests.NAnt.DotNet.Tasks.CscTaskTest.Test_ReleaseBuild() in c:\source\tools\nant\tests\NAnt.DotNet\Tasks\CscTaskTest.cs:line 72 3) Tests.NAnt.DotNet.Tasks.JscTaskTest.Test_DebugBuild : Error Executing Project at Tests.NAnt.Core.BuildTestBase.ExecuteProject(Project p) in c:\source\tools\nant\tests\NAnt.Core\BuildTestBase.cs:line 96 at Tests.NAnt.Core.BuildTestBase.RunBuild(String xml) in c:\source\tools\nant\tests\NAnt.Core\BuildTestBase.cs:line 80 at Tests.NAnt.DotNet.Tasks.JscTaskTest.Test_DebugBuild() in c:\source\tools\nant\tests\NAnt.DotNet\Tasks\JscTaskTest.cs:line 58 4) Tests.NAnt.DotNet.Tasks.JscTaskTest.Test_ReleaseBuild : Error Executing Project at Tests.NAnt.Core.BuildTestBase.ExecuteProject(Project p) in c:\source\tools\nant\tests\NAnt.Core\BuildTestBase.cs:line 96 at Tests.NAnt.Core.BuildTestBase.RunBuild(String xml) in c:\source\tools\nant\tests\NAnt.Core\BuildTestBase.cs:line 80 at Tests.NAnt.DotNet.Tasks.JscTaskTest.Test_ReleaseBuild() in c:\source\tools\nant\tests\NAnt.DotNet\Tasks\JscTaskTest.cs:line 66 5) Tests.NAnt.DotNet.Tasks.VbcTaskTest.Test_DebugBuild : Error Executing Project at Tests.NAnt.Core.BuildTestBase.ExecuteProject(Project p) in c:\source\tools\nant\tests\NAnt.Core\BuildTestBase.cs:line 96 at Tests.NAnt.Core.BuildTestBase.RunBuild(String xml) in c:\source\tools\nant\tests\NAnt.Core\BuildTestBase.cs:line 80 at Tests.NAnt.DotNet.Tasks.VbcTaskTest.Test_DebugBuild() in c:\source\tools\nant\tests\NAnt.DotNet\Tasks\VbcTaskTest.cs:line 66 6) Tests.NAnt.DotNet.Tasks.VbcTaskTest.Test_ReleaseBuild : Error Executing Project at Tests.NAnt.Core.BuildTestBase.ExecuteProject(Project p) in c:\source\tools\nant\tests\NAnt.Core\BuildTestBase.cs:line 96 at Tests.NAnt.Core.BuildTestBase.RunBuild(String xml) in c:\source\tools\nant\tests\NAnt.Core\BuildTestBase.cs:line 80 at Tests.NAnt.DotNet.Tasks.VbcTaskTest.Test_ReleaseBuild() in c:\source\tools\nant\tests\NAnt.DotNet\Tasks\VbcTaskTest.cs:line 74 Total time: 3 seconds. BUILD FAILED John C Barstow --- This SF.Net email is sponsored by: INetU Attention Web Developers Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers --- This SF.Net email is sponsored by: INetU Attention Web Developers Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
RE: [nant-dev] Formatting, #Regions, and CVS Keywords
2.) Reformat all files removing tabs and following the guidelines in the nant coding conventions. (http://sourceforge.net/docman/display_doc.php?docid=6080group_id=31650). Whoever is commiting changes may want to run Artistic Style (http://astyle.sourceforge.net/) on the source files to enforce code formattingconventions.
RE: [nant-dev] documentation error
Maybe working backwards from my original problem would shed light on this. Let's take an example...right now in the nightly builds there is support for a tag called 'nunit2'. How would someone get access to documentation on this? The correct answer is: Do a point release, already. The current stable release is over six months old and is missing some fairly major functionality. The product's not at 1.0 yet, so bugs and workarounds are acceptable (as long as they are documented). It's post-holidays; surely at least one of the committers can get a release out the door. --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
[nant-dev] Inherited property values
I've been wrestling with getting a 'debug' value to cascade properly, and am
beginning to think there's an issue with how properties are defined.
So, this is what I tried:
file1:
project name=file1 default=rel
property name=debug value=true /
target name=rel
property name=debug value=false /
nant buildfile=file2 inheritall=true /
/target
/project
file2:
project name=file2 default=compile
property name=debug value=true /
target name=compile
csc debug=${debug} ... /
/target
/project
Expected results in target='compile'
1) 'nant -f:file1' should result in debug=false (actual was true)
2) 'nant -f:file2' should result in debug=true
3) 'nant -f:file1 -D:debug=true' should result in debug=true
4) 'nant -f:file1' -D:debug=false should result in debug=false
Case 1 appears to be incorrect. Is inheritall begin ignored? Do I not
understand properties? Why are the other three producing expected results?
John C Barstow
---
This SF.net email is sponsored by: Scholarships for Techies!
Can't afford IT training? All 2003 ictp students receive scholarships.
Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more.
www.ictp.com/training/sourceforge.asp
___
Nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers
[nant-dev] Reference handling
I can't seem to figure out the syntax to refer to assemblies in the global assembly cache. The syntax seems to work for the 'standard' assemblies like System.Drawing.dll, but referencing an assembly like ADODB.dll or nunit.framework.dll results in all kinds of compiler errors with nant. Is this a known issue? If so, what is the proper syntax? I'm asking this here (rather than in nant-users) mainly because I think the nunit.framework, Version=2.0.6.0, Culture=neutral, PublicKeyToken=96d09a1eb7f44a77 syntax should be accepted in the references section. It doesn't seem to be with the latest snapshot, and I think that's a bug. If people agree, I'll look at updating the csc/vbc tasks. John C Barstow --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
RE: [nant-dev] FAQ: The next NAnt version
It's been a week since I've seen anything word on this. Is anything happening? John C Barstow --- This SF.net email is sponsored by: Microsoft Visual Studio.NET comprehensive development tool, built to increase your productivity. Try a free online hosted session at: http://ads.sourceforge.net/cgi-bin/redirect.pl?micr0003en ___ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
RE: [nant-dev] FAQ: The next NAnt version
I am aware of the NUnit to NUnit 2 migration, and have been able to use the latest NAnt and NUnit 2 using the exec task/console runner workaround. Hi, first-time user - just figured out that 0.7.9 is badly out of date, now using daily snapshot. I need to set up an NUnit2 task for my project - can someone explain the workaround for me? All my tests are written with NUnit2, so I can't backport (easily) to NUnit 1. John C Barstow --- This sf.net email is sponsored by: Battle your brains against the best in the Thawte Crypto Challenge. Be the first to crack the code - register now: http://www.gothawte.com/rd521.html ___ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
[nant-dev] Nant contrib tasks?
I can't seem to find any of the tasks the change log says were moved to Contrib. The NAntContrib project appears not to have any files available for download, and the stable snapshot did not appear to create a contrib directory. I'd like to contribute a couple of tasks, but I'm not planning on duplicating existing work. If anybody can point out the contrib stuff, I'd be much obliged. John C Barstow --- This sf.net email is sponsored by: To learn the basics of securing your web site with SSL, click here to get a FREE TRIAL of a Thawte Server Certificate: http://www.gothawte.com/rd524.html ___ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
