Interested in working on Nant related work and builds in Burnaby
(Vancouver), BC, Canada for Electronic Arts? Send your resume directly
to me [EMAIL PROTECTED] and I'll see what can happen.
Feel free to contact my directly for any specifics. Note the position
is only for the Burnaby office at
Two years ago today (July 18) NAnt was first released on Sourceforge.
Thanks to everybody for all the hard work put into the project.
---
This SF.net email is sponsored by: VM Ware
With VMware you can run multiple operating systems on a single
Due to the non stop spamming of the -dev list I've closed off non list
members from posting to this list. If you want to post to this list you
will first have to join.
---
This SF.Net email is sponsored by: INetU
Attention Web Developers
In an effort to one up people I'm going to try to get nant working under
mono on my iBook (OS X).
My vision is for the core nant distribution to work on any .NET platform
with platform specific tasks in different dll's. I think a global
property should control what compiler the csc task uses.
I too think the CVS list is better suited for this (but it was cool
getting the first message).
-Original Message-
From: Scott Hernandez [mailto:[EMAIL PROTECTED]]
Sent: Monday, December 09, 2002 4:14 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: [nant-dev] [nant] Build
Placing the responsibility of getting a release out on the project
admins isn't going to work if the past is any indication of the future
:)
The best way to get a release done is for a number of people to take a
nant-snapshot and QA it to the level that they would feel comfortable to
say that
What do people think of these two global task attributes. When I say
global I mean all (or almost all tasks would implement these - like if,
unless, etc..)
1. force
This attribute would have to be implemented on a task by task basis but
I think that any task does dependency checking should
I like both of them. However, I have some issues with the force
attribute.
I would think the purpose of force would be to ensure that for a
one-time build everything got built. That is, it wouldn't normally be
used. I might use it if I thought that my objects were out
of date, or
if
I'm not quite so convinced about this one. Are there any
specific tasks
you'd like to see that supported this? (besides exe)? I'm
also worried about
the possible complexity it would bring to tasks just to get
them to print a
simple message. For example, how would it relate to Verbose?
While looking through the code, though, I noticed that the code in
PropertyDictionary's indexer is:
set {
if (!_readOnlyProperties.Contains(name)) {
Dictionary[name] = value;
}
}
Now, this will silently be ignored if the property is
readonly. Somehow, I
don't think this is
It might be uesful to be able to poke values into the
environment from the
build file for various tasks that use them.
When I get around to syncing my version and the public version of nant
I've made a change to the exec task that does something like this:
The task looks for properties
The correct way to do this is to write the command line used to compile
the assembly into the output folder as a separate file. The
csc/compilerbase task then reads that file and compares it to what it is
about to use to compile the assembly.
If they are different run the build.
If it is
That is why the command line used to compile the assembly should be
saved and checked. If you changed the build file and it causes a
command line setting to be changed the build will get executed. This
gives you exactly what you are getting by depending on the build file
except that if you also
Yes. The Nunit team is already getting this into NAnt. NAnt will be
using Nunit 0.8 and ideally Ndoc 2.0 for the 0.8 release.
-Original Message-
From: Griffin Caprio [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, October 08, 2002 4:48 PM
To: [EMAIL PROTECTED]
Subject: [nant-dev] NUnit
used?
Christopher Barkley
-Original Message-
From: Shaw, Gerry [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, September 25, 2002 8:49 PM
To: Barkley, Chris; [EMAIL PROTECTED]
Subject: RE: [nant-dev] Adding Validators
Do I need to update
any files to tell it that this new
Do I need to update
any files to tell it that this new validator?
To be honest Chris I don't know. I suggest you set a breakpoint on the
BooleanValidator code and trace through it. I believe the code is in
the Element.cs that will be of interest.
Feel free to comment the
Title: Commenting out tasks
Poking around in the Project.InitializeProjectDocument() I've noticed that if task names are prefixed with # they won't be executed.
I'm not sure who implemented this but it seems like an undocumented hack to me. Are there any objections to removing this?
Yeah, after a bit of investigating I now see that it wasn't put in there to
allow for commenting out tasks but it serves a real purpose.
It feels like there should be a better way to do this but for now I'll just
leave it as is.
---
This
Oh yeah, you could also just import the environment variables using the
sysinfo [1] task if you do want to use environment variables - which I
don't think is a good idea if you expect your builds to work right out
of the box.
[1] http://nant.sourceforge.net/help/tasks/sysinfotask.html
What do people think of this addition to the format of filesets? Look at
the sources element of the build task. The build task is my own
private task. I thought it would be better to include the entire buildfile
in full so that if people could come up with a better syntax they could edit
the
Would anyone object to moving the ExpandProperties() method currently
defined in the Project class off to PropertyDictionary itself? I think it is
more appropriate there,
Sounds like a good plan.
---
This sf.net email is sponsored by:
What's the benefits? I can't see from here.
* I've created a custome task called component that works like this:
component buildfile=source/console/default.build/
component buildfile=source/gui/gui.build/
This task sets the following properties:
component.console =
I think its a good idea. Howver the outer tag should probably be
propertygroup or somthing like that. I think the . seperator is fine.
Do others feel strongly about this? I have it working with property
prefix=. I like it being all in one task so that when the user reads
the docs for
The nunit task will now look at the xml test results date stamp and
contents (looks for failures or errors). If the results datestamp is later
then the assembly's datestamp and the results show now errors or failures
the tests will be skipped.
This makes working on other nant tasks much faster
AFIK nobody is working on the SQL task. I think ADO.NET should be
considered cross platfrom. I believe I've heard that Mono is providing an
implementation of that API.
-Original Message-
From: Adrian-Bogdan Andreias [mailto:[EMAIL PROTECTED]]
Sent: Thursday, July 25, 2002 2:42 AM
To:
I want to populate a project property with output from a task. Is this
possible?
Since the output could be in almost any format I'm not sure how this would
accomplished. The Nant buildfile shows how to write a script to perform
this task. It parses the AssemblyInfo.cs with a regular
From a different point of view a task that would create a .xxproj from a
portion of a build file would also be very cool.
I've been using nant to build C++ projects but I like working in the VS IDE.
I use nant for all the building via an external tool hookup but I also have
a fake project so
27 matches
Mail list logo
