Ok, after the feedback I've received we won't do the master/ version/ thing
as it seems like cvs works quite a bit different than Perforce. If we need
to do a branch to support a release I'll ask for some expert CVS advice.
I did go ahead with the src/ refactoring. You will want to prune the empty
directories with the -P option, use this cvs command:
'cvs -P update'
The build file has also changed so that new task projects can be easily
added without changing the build file. This would be how you would add
custom tasks that are unique to your own project.
To do a full build of everything to create a release package use this
command from the nant directory:
'bin\nant.exe release package'
If you are wondering why I split the DotNetTasks it was because my goal is
to make the NAnt.Console and NAnt.Core assemblies run under Mono so I can
use nant under linux to build C++ projects. I believe nant should always
come out of the box being able to do everything to build .NET applications
but if people want to use it for some other reason they shouldn't have to
drag around the Nunit, Ndoc.* and SharpZip assemblies. The tasks in
NAnt.Core should not reference any other assemblies other than what is
specified in the Ecma standard. That said the <script> task does make
reference. I'm not sure what to do about that at this time.
My long (3-6 month) goal is to do a 0.8 release very soon. A 0.9 release
that will be feature complete (~3-5 months) and than a final 1.0 release (a
month after 0.9).
After the 1.0 release I hope that nant will become quite stable and most of
the work will be placed into the NAntContrib project.
Features I'd like to see for the 0.9 release are:
* functions, so we can write <fail if="${equals(${name},'bob')}"/>
* improved <fileset> so that tasks like the <zip> task or C++ compiler tasks
would be able to associate properties with groups of files in the file set.
I'd like this to be generic rather than a special case for each task that
needs something special with the fileset. Not sure if this is possible>
* a standalone nant gui runner, possibly with a very simple debugger so you
can step through your build, set breakpoints, and watch property values.
Comments and mail bombs are welcome. I'm sorry if this breaks a bunch of
stuff but we needed to do this as a project. It would have never gotten
easier so I figured we might as well bite the bullet.
Gerry
-------------------------------------------------------
This sf.net email is sponsored by: Dice - The leading online job board
for high-tech professionals. Search and apply for tech jobs today!
http://seeker.dice.com/seeker.epl?rel_code=31
_______________________________________________
Nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers
