RE: [nant-dev] New task idea
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 that I can easily launch the debugger and give a clue to VS.NET as to what files to parse for intellisense. --- This sf.net email is sponsored by: Jabber - The world's fastest growing real-time communications platform! Don't just IM. Build it in! http://www.jabber.com/osdn/xim ___ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
RE: [nant-dev] Property question
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 expression to grab the version number. What you are wanting is a pretty cool feature but I'm not sure how it would be implemented in a general way. I'd be interested in hearing your thoughts on the list. --- 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] task: 36894 sql
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: [EMAIL PROTECTED] Subject: [nant-dev] task: 36894 sql Hi guys, Can I start working on task 36894 sql or somebody is already working on it ? Do you think that ADO.NET can provide a cross platform / general approach ? If not, what else ? --- This sf.net email is sponsored by: Jabber - The world's fastest growing real-time communications platform! Don't just IM. Build it in! http://www.jabber.com/osdn/xim ___ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers --- This sf.net email is sponsored by: Jabber - The world's fastest growing real-time communications platform! Don't just IM. Build it in! http://www.jabber.com/osdn/xim ___ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
RE: [nant-dev] property task change
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 property they understand everything about it. Note that they can be nested as well. Ie, property prefix=win property prefix=vc7 property name=cc value=cl.exe/ /property /property Would give: win.vc7.cc = cl.exe I don't see a need for allowing custom seperators - it just seems to me that it would add unnecessary confusion. '.' is already a pseudo standard by its use for 'nant'. properties. I agree for most cases but it doesn't really hurt to add it and it adds the ability to use it in ways we haven't thought of. On a slightly different not it would be nice if we extended -projecthelp to show all global properties ( or maybe a different option ). There was a question on Nant-Users about how to reference environment variables. If you could get a dump of all env, nant and custom global props it would help the learning process. I'm thinking of having a special type of property called an option that build files have that are designed to be set by the user. So --projecthelp would display a list of the targets and build options. Ideally a gui tool would be able to show a nice dialog of the build options. When you save a group of build options you save a build configuration. So people send in your votes on these topics: 1. propertygroup name=win or property prefix=win 2. separator attribute or no separator attribute --- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1refcode1=vs3390 ___ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
[nant-dev] nunit task update
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 as you don't have to keep running the unit tests for assemblies you haven't touched. --- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1refcode1=vs3390 ___ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
RE: [nant-dev] Recursively expanded properties
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 = source/console/default.build
component.gui = source.gui/gui.build
component.all = console gui
I can now iterate over each of the components in my buildfile using:
foreach type=String property=current in=${component.all}
nant buildfile=${component.${current}}/
/foreach
* It opens the door for functions. For example:
property name=date value=${guid()}/
This would set the property 'id' to a guid. If the function takes
parameters you need to expand those as well. Ie,
echo message=id is '${string-length(${id})}' characters long./
---
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone? Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1refcode1=vs3390
___
Nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers
RE: [nant-dev] Moving Project::ExpandProperties
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: Jabber - The world's fastest growing real-time communications platform! Don't just IM. Build it in! http://www.jabber.com/osdn/xim ___ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
RE: [nant-dev] patch to support resolving properties from environment vars
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 --- In remembrance www.osdn.com/911/ ___ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
[nant-dev] Fileset change
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 file.
Basically I'm trying to make this file as human readable as possible so
people that aren't familiar with XML can see what is going on and add/remove
some files from a project for a specific platform.
The files are delimited by whitespace. If your file has a space character
you should use the includes name=xxx/ format. Another option is to
delimit the filesnames by \n so that spaces could occur in the filename (or
path if the full path was used to include the file).
-- included build file --
?xml version=1.0?
project
target name=build
build type=Library name=system
includepath
${platform}
cmn
/includepath
sources
!-- include platform dependent code --
includes name=${platform}/*.cpp/
!-- depending on the platform include shared common source
files --
includes if=${platform} == win
win/*.cpp
cmn/detectself.cpp
cmn/emms.cpp
cmn/lowtimer.cpp
cmn/setenv.cpp
cmn/startup.cpp
cmn/systemlock.cpp
/includes
includes if=${platform} == ps2
ps2/*.cpp
cmn/setkbdstate.cpp
cmn/startup.cpp
cmn/systemlock.cpp
/includes
includes if=${platform} == xbox
xbox/*.cpp
cmn/setenv.cpp
cmn/setkbdstate.cpp
cmn/startup.cpp
cmn/systemlock.cpp
/includes
/sources
/build
/target
/project
---
In remembrance
www.osdn.com/911/
___
Nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers
[nant-dev] Commenting out tasks
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?
RE: [nant-dev] Commenting out tasks
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 SF.NET email is sponsored by: AMD - Your access to the experts on Hammer Technology! Open Source Linux Developers, register now for the AMD Developer Symposium. Code: EX8664 http://www.developwithamd.com/developerlab ___ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
RE: [nant-dev] Adding Validators
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 BuildAttributeAttribute.cs class so the next person doesn't go through your pain with any info you find. Thanks for your help. Thanks for yours. --- 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] Adding Validators
Something is broken. Thanks for letting us know. Some unit tests are
going to be needed to catch the fact that the task attribute validators
are not being called.
-Original Message-
From: Barkley, Chris [mailto:[EMAIL PROTECTED]]
Sent: Sunday, September 29, 2002 5:22 PM
To: Shaw, Gerry
Subject: RE: [nant-dev] Adding Validators
Gerry,
The final verdict after hours of debugging I have found that
the Validators are never called. I have put breakpoints in
all of them and ran scripts that contained tasks that had all
of the validators defined for them. Not one break point was ever hit.
The following line in the element.cs file seems to be the one
that throws an exception when value does not match the return
value of the method.
if (propertyType.IsSubclassOf(Type.GetType(System.Enum))) {
try {
paramaters[0] = Enum.Parse(propertyType, attrValue);
} catch (Exception) {
// catch type conversion exceptions here
string message = Invalid value \ + attrValue +
\. Valid values for this attribute are: ;
foreach (object value in Enum.GetValues(propertyType)) {
message += value.ToString() + , ;
}
// strip last ,
message = message.Substring(0, message.Length - 2);
throw new BuildException(message, Location);
}
} else {
//
**
***
// This is the line that causes the exception
to be thrown
if they don't match
//
**
***
paramaters[0] = Convert.ChangeType(attrValue,
propertyInfo.PropertyType);
}
info.Invoke(this, paramaters);
}
I also removed all of the Validator lines from a few of the
tasks and run my test scripts against them with errors in the
value type of the attributes. I got the same exceptions with
them or without them. So I ask all of you out there, why do
these exist if they are not being 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 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 BuildAttributeAttribute.cs class so
the next person doesn't go through your pain with any info you find.
Thanks for your help.
Thanks for yours.
---
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] RecompileNeeded enhancement
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 missing, run the build. If it exists check for changed source files If they have changed, run the build. Depending on the datestamp of a build file is wrong as the build file can be changed for many reasons that shouldn't cause a recompile. -Original Message- From: Smith, Eric V. [mailto:[EMAIL PROTECTED]] Sent: Tuesday, October 08, 2002 6:31 AM To: [EMAIL PROTECTED] Subject: RE: [nant-dev] RecompileNeeded enhancement I've never been a fan of having everything recompile if the build file (or makefile) changes. I often make changes to the build file that don't invalidate any of the outputs. If anything, this should be optional, but I'd rather see it not included. What does everyone else think? -Original Message- From: Martin Aliger [mailto:[EMAIL PROTECTED]] Sent: Tuesday, October 08, 2002 9:26 AM To: [EMAIL PROTECTED] Subject: [nant-dev] RecompileNeeded enhancement Hi all, I draft one enhancenment to recompile-needed feature in CompilerBase. I'm heading to compile mono classes by nant. This is lot of subprojects/namespaces and files and this feature is desirable. 1/ Added support for changed .build projects --- 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 --- 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] RecompileNeeded enhancement
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 change something unrelated to the build (like add a comment) the build will not get executed. BTW: I do not like to nant clean;nant every time I change build file during devel of this. It's not so much problem to add rebuild rule anyway... BTW2: Many commercial environments do rebuild when project is changed. This is case of for sure rule - user could be very confused, when he e.g. enable Debug property in project and his debugger refuse to debug. And property task is not direct compile task - so isolating of csc into another file do not help. I see - there are much more cases where recompile is not needed, but... that few could confuse user a lot. --- 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] NUnit 2.0 Support?
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 2.0 Support? Are there any plans for NUnit 2.0 support from the nunit nant task? Specifically, support for the dynamic creation of test suites. -Griffin --- 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 --- 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] bug - Calling SysInfo Twice
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 that start with exec.env.* and will set environment variables for the executing process with those values. If you want to use the current environment you can use the sysinfo prefix attribute to exec.env.. --- This sf.net email is sponsored by: Access Your PC Securely with GoToMyPC. Try Free Now https://www.gotomypc.com/s/OSND/DD ___ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
RE: [nant-dev] bug - Calling SysInfo Twice
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 good behavior; it's confusing at best. Even more
cumbersome is the fact that some of the code is relying on this wicked
behavior. For example, unit tests for NAnt.Console actually
_check_ for this
silent change attempts to be ignored.
Any comments?
This behavior is for this situation: In your build file you define a
property (ie, debug) to have a default value.
property name=debug value=true/
And you use that property in your build file. You then want to override
that property on the command line so you use:
nant -D:debug=false
The nant console will add all properties on the command line as
readonly. When the property name=debug value=true/ task gets
executed the property will not be set to true but keep the value
specified on the command line.
I believe this is a valid use case but I share your concerns about the
subtle nature this might cause. I'm open to ideas to solve this.
---
This sf.net email is sponsored by:
Access Your PC Securely with GoToMyPC. Try Free Now
https://www.gotomypc.com/s/OSND/DD
___
Nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers
[nant-dev] Two new global task attributes
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 implement this attribute. Setting the value to true would cause the task to always execute even if the dependency checking tells it not too. The default would be false. 2. message If this attribute was defined and the task executed normally only the text in the message would be displayed on the console. Using this would allow you to document each step of the build file AND display nicely formatted results to the user. So instead of seeing: [mkdir] Creating directory D:\eagdf\project\NAnt\master/build/nant-0.8.0-deb ug/bin [copy] Copying 4 files to D:\eagdf\project\NAnt\master/build/nant-0.8.0-deb ug/bin You could see: [mkdir] Creating build directory [copy] Copying required assemblies to build directory The message attribute would be very useful on the exec task. --- This sf.net email is sponsored by: Influence the future of Java(TM) technology. Join the Java Community Process(SM) (JCP(SM)) program now. http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0003en ___ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
RE: [nant-dev] Two new global task attributes
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 something that isn't depended on is out of date. If that's the usage scenario, then this force option would be better off as a command line parameter instead of an attribute. If it really was an attribute, I'd either have to always have it present in the build file and have it conditionally turned on (ugly), or I'd have to edit the build file when I occasionally wanted to use it (even uglier). Or am I missing the typical usage of your proposal? No, your not missing anything. I think I've embarssed myself again by sending out a proposal without totally thinking it through. I think the usage you want is somehting like: nant -D:force=true build This would need to set something (a property called nant.force?) that tasks should look at? Ugg... I see you what you mean. It's getting a bit ugly. Lets put that on the back burner until a good solution comes along. The message attribute is the more interesting of the two anyways. --- This sf.net email is sponsored by: Influence the future of Java(TM) technology. Join the Java Community Process(SM) (JCP(SM)) program now. http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0003en ___ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
RE: [nant-dev] Two new global task attributes
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? WHich one of them would get priority? Well tasks would have the final say as to what to do (since they'll have to be implemented). Think of it as additional information as to what should be displayed if everything goes according to plan. In a -verbose setting or error condtion I'd the message would still be displayed along with any additional information. I'll implement it just on the exec task for now and see how that goes. If we like it for more tasks we can move the code. --- This sf.net email is sponsored by: Influence the future of Java(TM) technology. Join the Java Community Process(SM) (JCP(SM)) program now. http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0003en ___ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
RE: Re: [nant-dev] FAQ: The next NAnt version
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 this is a stable release that will add value to users. Needlesss to say you should agree on the date of the snapshot. Once that is done I'm sure one of us can go through the painful process of trying to convince SourceForge to post a release. --- This SF.net email is sponsored by: The Sourceforge Network Survey Take Our Survey and You Could Win a $500 Gift Certificate! http://ugamsolutions.com/psurvey/osdn/SourceForge/index_sourceforge.htm ___ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
RE: [nant-dev] [nant] Build Successful
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 Successful This is great information, but I wonder if maybe we should not send this out to the dev-list on every change. How about something along these lines: 1.) Send out status email(both success and failure) to the cvs list (people that are tracking cvs changes) 2.) Send email to the people doing check-in if a failure occurs snip/ If the cvs list isn't appropriate, maybe we should create a new list for automated build status reports. --- 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] Mono Support
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. For example, property name=csc.program value=/usr/local/bin/mcs/ property name=csc.style value=Mono/ property name=csc.program value=C:\windows\Microsoft.NET\Framework\v1.0.3705\csc/ property name=csc.style value=Microsoft/ property name=csc.program value=??/ property name=csc.style value=DotGnu/ By default the csc task should work out of the box (ie, MS on Windows, Mono on Linux) but there should be a clean way to override the compiler. --- 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] Posting restriction
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 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] Happy 2nd Birthday NAnt
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 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
[nant-dev] Job Oppurtunity
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 this time. --- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_idG21alloc_id040op=click ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
