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
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
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
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
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.
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]
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
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
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
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
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
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
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
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
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
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.
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,
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
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
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
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
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
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
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
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 /
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
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
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 -
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
29 matches
Mail list logo
