Gerry Shaw wrote:
Could someone go into a little more detail here? (I'm a
little knew to nant and trying to catch up :)
-Original Message-
From: Gerry Shaw
Why not have the element class have a default
implementation based on
the Attributes and if a task chooses to override this
Scott Hernandez wrote:
I would agree that they do not need to be unique. But task names do,
right?
yep
BTW. Maybe we should use a scheme like I described below to guarantee we
don't have dupl. task names defined. Right now, the first named task
that matches is always returned.
Thats true. We
There should be some feedback that there were no targets to build.
Somthing like No default targets found and then the project help ...
Ian
If nant is run without any target, and no default target is supplied via
the project element, what should the behavior be?
I suggest that the list of
Scott Hernandez wrote:
I was thinking that the config file would spell out the explicit (but
not absolute) paths for loading task Assemblies. And there you would add
more entries if you wished. The default behavior would disappear and the
new default would be to use the config file. I also
Committed
Ian
Subject:
NAnt patch to support MCS-style command line arguments
From:
Martin Baulig [EMAIL PROTECTED]
Date:
26 Apr 2002 21:43:43 +0200
To:
Gerry Shaw [EMAIL PROTECTED]
Hi,
here's a small
Sounds like a good plan. I was wanting to include it anyway as a binary.
Ian
I'd like to put SLiNgshoT in a public place so that others could possibly
work on it (especially since my time is so limited). Would the NAnt project
on SF be a good home? It seems like it doesn't really warrant it's
[EMAIL PROTECTED] wrote:
Here is a task for performing an UndoCheckOut from SourceSafe. It should
be pretty well documented.
On a side note... I copied the template from the work that Jason Reimer
did, should I include his name in the header or not? Just wondering what
the etiquette is?
Well
[EMAIL PROTECTED] wrote:
Here is a task for performing an UndoCheckOut from SourceSafe. It should
be pretty well documented.
On a side note... I copied the template from the work that Jason Reimer
did, should I include his name in the header or not? Just wondering what
the etiquette is?
Rob
Scott Hernandez wrote:
It does seem about time. But from what I see for the next milestone
release (.8), we aren't there yet.
Maybe a maintenance release would work. Like 0.7.9.*?
yep. I think we definately need somthing. That milestone description was
fairly arbitrary and there have been
I have access
the website. I can update it for a new release.
Id image the
release process is something like this.
Build Release
Upload to SF
Update Website
with new docs
Announce to the
world (I dont know who to announce
Scott Hernandez wrote:
Ive written a simple SCPTask,
that wraps scp.exe. For it to work, you need to have a setup that doesnt
require any password/pass-phrase to be typed. Im thinking about adding this
task to the newly (soon to be) formed NAntContrib project.
A nant-users list has just been set up. Subscribe in the usual manner.
Ian
___
Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
Scott Hernandez wrote:
I?d like to suggest that NAnt distribute the latest stable-release
NAntContrib assemblies in the bin folder. This way NAnt users will be
given all available tasks.
I?m not sure about docs and such; I guess we can come back to this
when we have a valid structure
Gerry Shaw wrote:
It does seem like a pretty good solution but what we have does work and
has been tested and isn't causing any problems that I know of. Its also
a lot fewer files.
Still it's a pretty good sample and I'll likely use it in other
projects.
Thanks
A sample just (a few
Scott Hernandez wrote:
We need to do something. This code fails because there is no file
associated with the document.
XmlDocument doc = new XmlDocument();
XmlElement project = doc.CreateElement(project);
XmlElement echo = doc.CreateElement(echo);
Scott wrote
My docs don't list XPathNavigator as implementing the IXmlLineInfo
interface. The object browser doesn't seem to show it either. Nor does
the IXmlLineInfo overview list any classes other than XmlTextReader,
XmlValidatingReader as implementers[1].
[1]
Scott Hernandez wrote:
My concern about the lines numbers was less about their need (or
accuracy), and more about the fact that the LocationMap generated errors
when the document is not file-backed. If we go with the DOM Extensions
then we can check for the IXmlLineInfo interface before we
John Lam wrote:
Does this sound like a reasonable patch to ExecTask.cs? Anyone want to
drop it in?
Committed.
Ian
---
Sponsored by:
ThinkGeek at http://www.ThinkGeek.com/
___
Nant-developers
I've just put together an installer for NAnt. It wraps up the nant
binaries and the extra tasks from NAntContrib into a single installer.
Right now you can download it from http://www26.brinkster.com/ianm74/.
Let me know what you think - any problems, improvements, ideas. It uses
nullsofts
Brad Wilson wrote:
Kevin Dente wrote:
True - but then you actually need the IDE installed on that machine. With
the CSPROJ task, you only need the free C# compiler (as in, you don't need
a VS.Net license for your build machine).
What part of the SDK creates and/or interprets .csproj
Someone has already done it. Check out
http://nantcontrib.sf.net/NAntAddinSetup.msi
Oops... I totally forgot about AddIns, guess I was a little quick to
jump on the most complicated solution.
Once I get a little more bandwidth (Aug. 5th app goes to prod), I'd be
willing to work on
Don,
What does your vbc task look like ? Are you adding the resources
properly using the arg element ? - see below an example of how to do
this. You can examine what resources have been added to an assembly
using ildsam - open the double-click on the MANIFEST node.
1) resgen the resx file
[EMAIL PROTECTED] wrote:
Hi All,
I have this sinking feeling that this is going to in fact be very difficult
as each task/target formats their log messages individually so that targets
have their name prefixed with a : and targets are wrapped like this [task]
at the point of log message
Kevin Miller wrote:
Word is there will be a release soon with a nice installer for both NAnt and
NAntContrib.
Kevin Miller
-
you can get the current version of the installer at
http://www26.brinkster.com/ianm74/
it's from cvs as of last week. It has a working NAntContrib dll with
Gerry Shaw wrote:
This was intentional and an oversight :) I didn't want those tasks in
the core tasks but I didn't want to lose them either. There should be a
NAnt.VisualCppTasks project added with the cl, link and lib task.
I'll add those on Tuesday. In the future I suspect these will live
Shaw, Gerry wrote:
What do people think of the following syntax for the property task:
property prefix=win-vc7.
property name=cc value=${vs-net.dir}\VC7\BIN\cl.exe/
property name=lib value=${vs-net.dir}\VC7\BIN\lib.exe/
property name=link value=${vs-net.dir}\VC7\BIN\link.exe/
Shaw, Gerry wrote:
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
Klemen,
You've hit it right on the head. Its been the cumbersome way it is for a
while now. What you've proposed is pretty much how it should be. It
shouldn't be too hard to implement. If you want to take a stab at it go
ahead. Otherwise I'll start on it. Its been irking me for a while now
Shaw, Gerry wrote:
For clarity here it is again.
If you went:
property name=alpha value=a/
property name=bravo value=b/
property name=charlie value=c/
property name=abc value=123/
echo message=${alpha}/
you would get (as you would expect):
[echo] a
If you went:
echo
I'm starting work on adding functions to nant and the syntax I was
thinking of using is this:
Are we sure we need this. No disrespect but couldn't we do a lot of
whats in these functions using the script task ?. Its a slipperly slope
to be taking - just look at how xslt has evolved from
I've checked in changes to compiler base so that it handles resources a
bit more nicely. this means that the following build fragment :
csc target=exe output=${outputname}.exe debug=${debug}
sources
includes name=Form2.cs/
includes
Thanks Ben. I've comitted both of your patches.
Ian
Ben Lowery wrote:
greetings,
i think i found a bug in CompilerBase::GetFormNamespace(). the bug occurs
when you use a resx file that has no corresponding .cs file (ie, if i had a
Transform.resx in my project, but no Transform.cs).
Gerry,
This new format is much more readable and easier to type than before.
The major downside I see is for people writing tools to read and write
the build file - or using xslt to transform it. You can no longer rely
on just the Xml api;s to read and write the build file. There now needs
Message-
From: Ian MacLean [mailto:[EMAIL PROTECTED]]
Sent: Monday, September 30, 2002 2:20 PM
To: Scott Hernandez
Cc: 'Barkley, Chris'; [EMAIL PROTECTED]
Subject: Re: [nant-dev] Adding Validators
I think some of this came out when InitializeAttributes was originally
rewritten. As it stands we
Arnoldus, Michael wrote:
I have changed the implementation of the Style task to use a TextWriter. I'm
hoping someone will look through my changes and check them in. Thank you in
advance.
comitted
Enjoy,
Michael Arnoldus
Tomas Restrepo wrote:
The fix seems to already have been commited by someone else.
that was me :)
However, may I argue _against_ this fix?
There are two reasons I don't like it:
a- It changes semantics. PropertyDictionary inherits from DictionatyBase.
Common semantics in all of .NET
Sorry about that. The right version is checked in now.
Ian
i could be completely wrong about this, but it seems as though the checked
in version of CompileBase from nov 7 expects the method
'GetManifestResourceName' to exist in ResourceFileSet. the version of
ResourceFileSet checked in to CVS,
Kevin Miller wrote:
Yep this is the way it works. We start the thread and someone goes off topic
and the powers that be never make up their mind.
OK valid point. And as one of the project admins I take my share of the
blame for this. Gerry Scott and I discussed a release last time and it
I agree that a lot of those tasks should be rolled into the main NAnt
project. I think there is still a place for NAntContrib as a place for
user submissions. The idea being that there is a lower barrier of entry
to the contrib project and the best - ie useful to most people tasks get
moved
Griffin,
I think the NUnit v2 support is rolled in. All the Nant tests seem to be
using the new format, ie with attributes. Someone who has worked more in
this area may know better what the state of it is.
As for development slowing down - I can only speak for myself. I've been
out of action
Rosemarie,
I tried the first link and I can download it fine. Maybe there was a
temporary outage or somthing.
Ian
Hi
I am trying to get this download from the
http://nant.sourceforge.net/snapshot site, but I keep getting a DNS
error, I have even tried the http://sourceforge.net/ site and no
After seeing new Scott's latest changes it looks like that code has been
moved to ConsoleDriver.cs. So I'll look at adding the changes there.
Ian
Brian,
thanks for your contribution
I just had a brief skim thru the code and it looks OK. As for style
conventions just the usual.
1. open braces
Scott Hernandez wrote:
+1 on echo supporting inline (text node) text.
yeah me too. Good idea.
Ian
I don't use the web based browser much, but it seems to work for me today
when I was checking on my changes.
- Original Message -
From: Brian Deacon [EMAIL PROTECTED]
To: [EMAIL
If they are excluded from the compiles then we probably aren't using them.
Ian
It seems like we are using the NUnit2 stuff and no longer using the
AllTests.cs files for our tests. Can anyone confirm this? If this is
true, I'd like to remove these files from cvs instead of just
excluding them
Aaron,
Can you please re-send this as a diff ? cvs diff -u. Its easier to
review and apply in that format.
Ian
All,
I made some changes to the ResGenTask.cs file that I would like reviewed and
committed. I was having difficulty using this and having the task create my
resource files with the
Sorry Aaron. I didn't see your comment about not having diff.
Ian
Aaron,
Can you please re-send this as a diff ? cvs diff -u. Its easier to
review and apply in that format.
Ian
All,
I made some changes to the ResGenTask.cs file that I would like
reviewed and
committed. I was having
This file is using the regkey
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\sdkInstallRoot to
find the current installation directory for the framework. However this
only gives you the install path for version 1.0. v1.1 is set at
sdkInstallRootv1.1. There will be a number of people
Gordon,
I'v added this task to NAntContrib. There is also the versionInfotask
which John Lam submitted a while ago. It does somthing similar but it
auto increments a buil number to write to the version info.
Ian
This might help you or somebody else, I've written a custom task for generating
Jeffrey McManus wrote:
I'm accustomed to thinking of docs as a part of the
deliverable package and as such, something that should
be checked in. I'm willing to accept that not
everybody does it that way, though.
Having docs checked in makes sense if they are edited as html. Ours are
You should post a patch to this list. read up on cvs diff, use the -u
option for readibility. Your contribution is welcome.
Ian
I made a pass
through all of them, correcting spelling mistakes and
adding content here and there using my tool of choice
(which happens to be Dreamweaver, but could
Sansone, Aaron wrote:
shameless_plug
I'd be willing to take a look at deploying a wiki to my NCode Sourceforge
project to see if it works. NCode is a VS.Net IDE Add-In that does code
completion from live templates (just like IntelliJ if anyone has used that).
urlncode.sourceforge.net/url
Mark,
This has been my approach as well. Have a .build file at a given
directory level be responsible for building itself and nested
subdirectories. I would often have a common .build file that contains
common propeties that all the other .builds would include.
Ian
Attached is an example of
Simon,
fyi there is another versioninfo task - written by John Lam in
NAntContrib. I haven't compared it to yours yet but it might be worth
looking at to see if there is some overlap.
Ian
Hi,
I recently found NAnt and decided to attempt to use it for creating a
nightly build system both at
Simon Steele wrote:
Hi Ian,
John's task (correct me if I'm wrong) is for updating AssemblyInfo.cs
files which are used for CLR style projects. The task that I've
developed is for updating VERSIONINFO blocks in resource script files
- those generally used for win32 projects such as myapp.rc or
Bryce,
Which build of nant are you using ? I seem to recall this being fixed a
while ago.
Ian
Using the examples available in the online docs for the 'zip' task as
part of a build script. The ZIP file is created successfully and has the
expected set of files except that the leading 2
();
} finally {
}
}
]]/code
/script
Ian
Was the CreatTask function created not for these kinds of things? Of maybe
It's just there for internal nant use?
-Original Message-
From: Ian MacLean [mailto:[EMAIL
, February 13, 2003 8:54 PM
To: [EMAIL PROTECTED]
Subject: FAQ Q, was (Re: [Nant-users] Emailing NAnt output using mail
task)
We should add this one to the faq on the wiki. :)
- Original Message -
From: Ian MacLean [EMAIL PROTECTED]
To: Chris Garty [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent
for more info.
I've got one small correction, though, my name's spelled Weakliem :-)
Doh ! Sorry about that.
Ian
Ian MacLean wrote:
After realizing that there was no FAQ and observing lots of the same
questions cropping up on the lists recently I've put together a first
draft of an FAQ. Thanks
Gert
If you want to delete a directory or file that doesn't exist, then this
should just be considered a successful execution of the task, shouldn't it
be ?
yep. And it will work that way for filesets I think.
Certainly if there's currently no means to check if a directory (or file)
actually
Brian Deacon wrote:
(and Ian, I thought you were gonna commit my vast improvement on
the echo task?)
Committed ! thanks.
Ian
---
This SF.net email is sponsored by: SlickEdit Inc. Develop an edge.
The most comprehensive and
forgot reply-all again .
---BeginMessage---
[EMAIL PROTECTED] wrote:
A good article, thanks for the link. IMO, It depends on the type of
application -- and the type of user. It also depends on how those items are
included.
Agreed. I'd just read the article yesterday so it was fresh in my
Simon,
I assume you are talking about the quiet attribute. I'm wondering how
this overlaps with previous discussions about logging level.
ie if the
logging level is at a certain level write the error otherwise
don't. I'm
not sure there is a need for the quiet attribute on individual tasks.
[EMAIL PROTECTED] wrote:
If I understand you correctly, you want me to remove the quiet attribute and always output a message in the log when you try to delete a file or directory that doesn't exist, right ?
yeah for now. I don't have a problem with the concept but I think we
should think
So the concensus seems to be : defer the patch until file/Directory
Exists functionality is available.
Ian
Hi,
I agree that we should perhaps decide not to commit this patch at all ...
But if the Delete task should continue to throw exceptions when you try to
delete a non-existing file or
Title: Message
I'm
already looking at this problem by having settings stored in the config file. ie
there would be a FrameworkCompilerDir and a FrameworkSDKDir paramater. These
values will accessible from tasks and changeable from the build file. There will
also be task specific settings so
it everywhere to keep
the codebase consistent rather than having it in some places and not others.
Ian
Hi Ian,
It's just a good programming practice to always specify the culture (FxCop considers it to be a rule violation when you don't specify the cultureinfo)
Gert
Ian
I just did a sync and I'm getting the same thing. The nightly build
seemed to run OK - there have been a bunch of cultureInfo related
changes since then - maybe somthing to do with that.
Ian
Hi Guys,
OK, is it just me, or is NAnt's build/test broken?
During build on my machine, when the unit
about adding a check to make sure that recursive (depth 5)
buildfiles fail by default. This would stop someone from accidentally
creating one.
I will look at it when I get back from shopping tonight :)
- Original Message -
From: Ian MacLean [EMAIL PROTECTED]
To: Tomas Restrepo [EMAIL
I just had a thought. The change I made means that the following
includes statement :
includes name=**/* /
will include both files and directories which might break somthing that
is only expecting to get files passed to it.
we could add
filesonly and
directoriesdonly
attributes on the fileset
Philip Nelson wrote:
--- Scott Hernandez [EMAIL PROTECTED] wrote:
I would like to see NAnt run on Mono. Does anyone want to volunteer to be the
point man on this?
For the next major release I'd like to see us provide a Mono distribution.
What parts of NAnt? I had gotten NAnt.exe to partially
Philip,
Trying to compile nant under mono. What I originally thought was an xml short
fall is actually a reflection shortfall:
element has more than one match for attribute_type
Anyway, the problem occurs trying to compile McsTask (and other times using
Mono with .net compiled assemblies).
There was a request some time back to allow multiple resource filesets
against a cscTask to enable adding resources to multiple namespaces. To
get this working I finally implemented support for the
BuildElementArrayAttribute. This enables you do do the following :
[BuildElementArray(
Gert Driesen wrote:
I'm trying to build a assemby using Mono 0.20 on Windows, but apparently
the Mcs task calls the mcs.exe, this will cause Mono to compile an
assembly using the .NET runtime instead of the Mono runtime.
The task should instead call mono mcs.exe [options]
I think *should* is
Tony,
The directories do get added to the Fileset, but under the
Fileset.Includes collection.
Changing the part of ClTask.cs that does the includes to reference
Fileset.Includes instead of Fileset.FileNames fixes that issue. However,
is it the correct, long term fix? Based on what you've stated,
Matthew Mastracci wrote:
I've manually applied Aaron's changes to my tree, cleaned up the style
to match the NAnt coding style and attached it to this message.
If noone objects, I'll check this in.
Looks ok to me.
?
Gert Driesen wrote:
As agreed, I implemented an Available task that allows you to check for the
available of a file or directory resource.
eg. available type=File resource=myfile.txt property=myfile.present
/
I used resource instead of file (or directory) for the attribute name,
so we can add
Gert Driesen wrote:
Is it possible right now to set a runtime that is defined in the settings
file but that doesn't exist on the system ? how will Nant react to that ?
This will cause an error. Frameworks that don't validate - ie their
sdk/framework paths don't exist aren't loaded into the
Matthew,
I applied your patches to Fileset.cs and directoryscanner.cs as well as
the new copytest.cs. The part of the patch fixing copy and delete failed
to apply against my tree - maybe because the patch isn't in -u format.
The following patch fixes directories getting treated as files in a
CLS compliance makes sense but I see no reason to exclude COM clients -
just because you get an fxCop warning.
Ian
Hi,
I created a patch that will make NAnt.Core CLSCompliant and that will no
longer mae NAnt visible to COM clients (which I don't think is necessary
anyway).
I'm not saying
Philip Nelson wrote:
I hit more on this later. If you have a default install, remove all of the
dlls from the bin directory and start again. Then, get rid of any classes that
have using Win32 in them.
Unfortunately I just added using Win32 to project.cs to support the
multiple runtimes. I want
I just the same poblem. Looking at the recent commits there is a change
to DirectoryScanner that stops exclude scanning from being recursive
which means its not excluding GetTaskTest.cs.
from marcs DirectoryScanner checkin:
Don't trigger a
recursive scan on exclude patterns.
Marc - whats the
Gert,
try now. It should be fixed.
I've removed the constraint that excludes aren't recursive. Everything
else is unchanged.
Ian
Hi,
I'm having problems building nant using the build file.
Apparently the excludes are no longer functioning, because the
'GetTaskTest.cs', the
? Is the
build failing on anyones local machines ?
Ian
Ian MacLean [EMAIL PROTECTED] wrote:
Gert,
try now. It should be fixed.
I've removed the constraint that excludes aren't recursive. Everything
else is unchanged.
Ian
Hi,
I'm having
Matthew Mastracci wrote:
the directory scanner should not trigger a recursive scan - only files
in blah/foo/bar need to be scanned. Unfortunately, I managed to mess up
the logic so that exclude patterns no longer work at all.
The strange thing is that the unit tests ran for the build I did.
Scott Hernandez wrote:
Sounds like a good feature... :)
+1
+1 for me too.
(In general I'd be happy to see the write-up without the code. If there are
any problems, they will come out in the tests, or from use. Other comments?)
I agree. Most of us with commit access will see it come thru on the
Scott Hernandez wrote:
+1 on release.
me too. We've added a lot of good stuff recently.
Also, I'm wondering if anyone would mind if I started adding the VS.NET
solution builder code to the NAnt CVS tree. It reliees heavily on
up-to-date code within NAnt (it uses a large number of core NAnt
Scott Hernandez wrote:
I want to reformat all the files and do the following:
1.) Wrap the license info at the top of the file in a #region, which
will make editing with vs.net (and others I believe).
+1
2.) Reformat all files removing tabs and following the guidelines in the
nant coding
Matthew Mastracci wrote:
Just a comment about the $Log$ keyword - the CVS in-line version log is
a little bit of a pain to handle sometimes. I think it would be okay if
wrapped in a #region, but some issues may crop up (especially with
regards to merging/branching). This page mentions some of
Jeff McManus wrote:
Hmm, would it be meaningful to have a NAnt task to call Artistic Style
automatically at build time? Has this been done already?
I'm not so sure thats a good idea. Its nice to be able to do this
automatically but on every build seems excessive.
Ian
-J.
-Original
I've created a new NAnt.Win32Tasks assembly to hold win32 specific
stuff. I've moved those tasks that fail to compile on linux in there to
start with so that I can move forward with getting NAnt building on with
mono/linux. Obviously compile on linux doesn't mean run on linux - the
Arjen Poutsma wrote:
I also wonder if the regex task i submitted will be added to the cvs, or whether it
needs to be improved first.
I've added it. Thanks
Ian
---
This SF.net email is sponsored by:
The Definitive IT and Networking Event. Be
Gert Driesen wrote:
Hi,
Will we actually be supporting (and maintaining) both the csc task and
mcs task for building mono assemblies ?
nope. I the csc task working on mono/linux with some tweaking. I'll
remove the mcsTask
Ian
We should decide as soon as possible what we're gonna do with this,
Gert Driesen wrote:
Hi,
I think we should add multiple framework support for the vbc task too,
similar to the support in the csc task.
That will allow nant to build vb applications targeting multiple .NET
frameworks and MonoBasic.
Shall I add support for this and supply you with a patch ?
I'll take a look at it. You're right it should only fail on circular
includes - that was the idea anyway.
Ian
Hi,
I want to create a hierarchy of included configuration files, where each
level of the hierarchy adds information.
eg. I want to have the following directory structure :
Arjen,
Until now, I've always used the XsdTask (from NantContrib) to generate my
typed datasets from xml schemas. I've found that using this this task has
several disadvantages:
* You can't use filesets to generate datasets from a collections of xml schemas.
Since my entire build environment is
LoadTasks task is implemented and committed. Pretty much how Tomas
described below except that if you're using a fileset it can take either
a path or an assembly attribute. The fileset behaves as you described.
for those who missed the discussion - the LoadTasks task is a
replacement for
.
-Original Message-
From: Ian MacLean [mailto:[EMAIL PROTECTED]
Sent: Friday, June 06, 2003 3:37 AM
To: Nant-Developers (E-mail)
Subject: [nant-dev] cvs re-org
The cvs-reorg has been done on the cvs server. You'll need to
checkout
a completely fresh client
Yeah - sorry about that. I was going to post a notice. In the last round
of cvs changes that directory got re-created but permissions weren't set
correctly. I'm waiting for the sf admins to fix it - its in their
support request queue. I'll post here when its done. Sorry for hte
inconvenience.
Good call Erv. I'd completely forgotten that foreach supported filesets.
Ian
Foreach already supports filesets.
Search the nant archives for a couple discussions that exactly solve
this problem (of recursively building) using foreach filesets.
-Original Message-
From: [EMAIL PROTECTED]
of course but we're not talking every system out there. We are talking
about cvs - the number 1 scm used by open source projects. I would argue
that the cvs tasks should ship with the core nant distribution simply
because a large number of nant users will find it useful. I do *not*
think that
1 - 100 of 439 matches
Mail list logo
