Gert Driesen wrote:
Hi,
Should we rename the NAnt.Zip(Tasks) namespace, assembly and directory name
to NAnt.Compression (or if someone can come up with a better name ...), now
that I've also added tar support ?
sounds good to me.
Ian
Gert
---
Gert Driesen wrote:
Hi,
Right now, the zip & tar flavors of our distributions have the same content.
I wonder if it makes sense to include the SDK docs in HTML Help format for
the (gzipped) tar flavor, as these target *nux anyway.
that probably doesn't make much sense if we assume that Windows u
Gert Driesen wrote:
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Eric Fetzer
Sent: woensdag 17 november 2004 17:39
To: Gert Driesen; 'NAnt Developers'
Subject: RE: [nant-dev] Fwd: VB task not working
Gert,
Thanks, but I tried that. I already had
Neil Cowburn wrote:
I have a number of targets of various type (code compilers, file system
management, custom scripts) and I'd like to separate them out into
individual files and reference them from a master build file. I thought the
task would meet my requirements, but since it executes the targ
estion - but you can call specific targets in an included build file from a master file. And as Troy pointed out you can call individual targets using the nant task as well.
Ian
--Neil
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Ian
MacLean
Sent: 18
Tim Noll wrote:
I'd like to propose adding extension objects to the style task. More
information about extension objects can be found here:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpguide/html/cpconXsltArgumentListForStylesheetParametersExtensionObjects.asp
The build file t
Martin Aliger wrote:
ps : I've got a small nant function called is-assembly (to
determine
whether a file is a valid assembly or not). Is it worth
contributing ?
I'm using it to separate my "legacy dll" from assemblies. I know
there's the get-assembly-name trick, but mayb
sure it works against the 0.85 code base. And, yes,
extension objects will have to have a default parameterless
constructor for now.
Regards,
Tim
On Mon, 22 Nov 2004 12:11:27 +0900, Ian MacLean <[EMAIL PROTECTED]> wrote:
Tim Noll wrote:
-
stuff has been committed to cvs.
Ian
Tim
On Thu, 02 Dec 2004 21:10:16 +0900, Ian MacLean <[EMAIL PROTECTED]> wrote:
Tim Noll wrote:
Here are the changes needed in order to add extension objects to the
style task. This change consists of three files:
NAnt.Core\Tasks\StyleTask.cs
Gert Driesen wrote:
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Steve Jansen
Sent: vrijdag 3 december 2004 17:19
To: [EMAIL PROTECTED]
Subject: [nant-dev] task question
Hi again,
I have a question about the task and the
project::get-buildfile-p
Ian MacLean wrote:
Gert Driesen wrote:
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Steve Jansen
Sent: vrijdag 3 december 2004 17:19
To: [EMAIL PROTECTED]
Subject: [nant-dev] task question
Hi again,
I have a question about the task and the
Gert Driesen wrote:
- Original Message -
From: "Ian MacLean" <[EMAIL PROTECTED]>
To: "Ian MacLean" <[EMAIL PROTECTED]>
Cc: "Gert Driesen" <[EMAIL PROTECTED]>; "'Steve Jansen'"
<[EMAIL PROTECTED]>; <[EMAIL PROTECT
Jaroslaw Kowalski wrote:
I like the wrapper idea. I never understood why NAnt included NDoc
instead of just spawning it. Same thing applies to NUnit.
It would be cool to have a common way of detecting the packages
locations. I think we can use pkgconfig approach on Unix and
AssemblyFolders or
Wen Ching Chua wrote:
I try to find on the internet on how to achieve this in C#, but still
can't find any good resources till i downloaded Nant.
But there are too many codes inside Nant, and i have no idea which
part of Nant code that can achieve this below.
Greco Giuseppe wrote:
Hi all,
Why doesn't the task support the NDoc argument "xmldoc"
(see http://ndoc.sourceforge.net/usersguide.html)?
NAnt assumes that XML files generated by the C# compiler are
always located in the same directory as the compiled assemblies.
Don't you think that we should add
Giuseppe Greco wrote:
Do you plan to localize NAnt?
I think it would be a good idea.
If yes, how are you going
to manage translations? Actually, compiled assemblies and
XML files generated by the C# compiler are kept togheter
in the same directory, letting NDoc find them and do its
job.
looks
Hi Swoogan,
I wrote an installer script for Inno Setup
(http://www.jrsoftware.org/isinfo.php) for NAnt distribution around my
office and I would like to contribute it. Besides copying the files, it
adds the nant bin directory the environment path and creates a registry
entry pointing to the insta
Greco Giuseppe wrote:
Mono source code does not contain documentation comments; XML stubs
are generated via reflection with assembler.exe/updater.exe. Miguel
told me that they want to keep user documentation separated from
source code, meaning the /doc feature of the C# compiler is useless...
plan on doing that today. My last build was 1/11 and it worked fine then.
John Cole
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jim Geurts
Sent: Tuesday, February 15, 2005 8:24 AM
To: Ian MacLean
Cc: Swoogan; nant-developers@lists.sourceforge.net
Subjec
Greco Giuseppe wrote:
Ian,
looks ok - but why not get AssemblyName dynamically using :
Assembly.GetCallingAssembly() ?
then you only need to define the RM class once in NAnt.Core.
You're right... attached to this email you'll find a better
version of RM.cs (RM stands for [R]esource[M]anage
Perhaps we should explore a new mechanism for extension libraries in
NAnt, with inspiration taken from the Java jre/lib/ext idea...
4) Install NAntContrib to a different folder, and add an xml
descriptor/locator in NAnt/bin/ext which describes the library.
NAnt could scan the bin/ext folder for
Greco Giuseppe wrote:
I figured that one out :). We could probably call it
NAnt.Core.ResourceUtils or somthing like that.
That's up to you... but such a name is a little bit too long and
uncomfortable to be used often...
you think ? Show me some classes in the core framework that have 2
l
The first step would be to create the resource files
(NAnt.Core.en-US.resx,
NAnt.DotNet.Task.en-US.resx, etc.),
we can just start with NAnt.Core.resx for the default ( US english )
language.
then replace hardcoded strings with
RM.GetString("Message_Id") - or whatever name you want, and finally a
Ian MacLean wrote:
output="${build.dir}/${package.name}/lib/${culture}/${assembly}.resource
s.dll"
culture="${culture}">
...
value="-res:${build.dir}/${package.name}/lib/${default.resources}" />
Ian MacLean wrote:
Ian MacLean wrote:
output="${build.dir}/${package.name}/lib/${culture}/${assembly}.resource
s.dll"
culture="${culture}">
...
value="-res:${build.dir}/${package.name}/lib/${default.reso
Greco Giuseppe wrote:
...
will work just fine.
Just a question: does the element automatically
embed the defalut resources into the assembly, or is the
element still necessary?
If the name of the .resx file contains a culture part it will package it
up with any
Hi Justin,
James, Justin wrote:
What are the requirements for the Nant Documentor to actually generator the nant style documentation? I have a bunch of custom task that I have built but when I use the nant documentor all of the tasks/properties/types show up in the web output but it does not inclu
Giuseppe Greco wrote:
Ian,
attached to this email you'll find a tar.gz containing the
RESX skeletons. Could you please integrate them into the
project and import them into CVS?
The next steps would be:
1. Decide a standard for string IDs
How about somthing like 'NA1001' for errors and warnings.
James, Justin wrote:
Ian
Here is the csc and ndoc tasks from my build file.
well that mostly looks ok. The only thing I can think of is that :
probably won't include NAnt.Core.dll unless you have a build/bin/bin directory.
I
Greco Giuseppe wrote:
How about somthing like 'NA1001' for errors and warnings.
Could not find a '{0}' file in '{1}'
Some descriptive comment
What about this? Could be a valid alternative?
Error messages:
Could not find a '{0}' file in '{1}'
Some descriptive comment
o
Greco Giuseppe wrote:
Hmm - well I'd like the keep the number in there - for
errors/warnings
at least. It will make finding the use of a given error
message easier
later on.
Okay, but tell me which one of the following formats:
Could not find a '{0}' file in '{1}'
Some descriptive
Greco Giuseppe wrote:
Hi Ian,
I think it would be preferable to have a common
resource assembly (e.g. NAnt.Resources.dll).
you mean all resources for every assembly all in a single resources
assembly ? - I don't much like that idea at all. Resources should be
located together with the assembl
Ian MacLean wrote:
Greco Giuseppe wrote:
Hi Ian,
I think it would be preferable to have a common
resource assembly (e.g. NAnt.Resources.dll).
you mean all resources for every assembly all in a single resources
assembly ? - I don't much like that idea at all. Resources should be
lo
Greco Giuseppe wrote:
what's about something like that? Giving the following resource files
Global.resx
Another.resx
... .resx
we could have a separate resource manager for each resource file,
This means storing *all* the resources in a single assembly
I don't quite understand how your impl
Greco Giuseppe wrote:
what's about something like that? Giving the following
resource files
Global.resx
Another.resx
... .resx
we could have a separate resource manager for each resource file,
This means storing *all* the resources in a single assembly
I don't quite understand how your im
Gert Driesen wrote:
Hi,
Right now, build authors cannot control whether references are copied to new
projects.
I decided to add support for this (using a inheritrefs attribute on ),
and while doing so I decided to make a breaking change here: references will
now no longer be copied to new projects
Troy Laurin wrote:
Okay, I no longer like css. It seems like every single web page I try
to design requires some combination of relative and absolute sizes
that is difficult to impossible to achieve in css. For me, anyway.
Basically this means I don't have anything html-y to show for my
efforts,
Mike Roberts wrote:
task for this purpose. The included project
(build file) can just contain a project element and a set of properties to
set in the parent project.
Good idea. Better than the
sanjoy wrote:
Dear All,
I want to know the following.
1. Get a report from CVS History file for all those files updated
after certain tag date for a given module. There are subdirectories
under the given Module.
2. The script should ask for the tag date.
3.Generated report should contain user na
Gert Driesen wrote:
Hi John,
I just forgot to commit a small change, hold on a sec (or in case you're
using anon cvs, a little longer).
btw John,
I was meaning to ask - how is that msi working out for you ? I'd like to
start adding it to out download page for releases. What do you think Gert ?
Gert Driesen wrote:
-Original Message-
From: Ian MacLean [mailto:[EMAIL PROTECTED]
Sent: donderdag 21 april 2005 3:35
To: Gert Driesen
Cc: 'John Cole'; nant-developers@lists.sourceforge.net
Subject: Re: [nant-dev] compiling NAnt and NAntContrib to
generate MSI...
Gert Dri
Troy Laurin wrote:
Anyway, I might have a play with it over the next few weeks, and if I
don't find any nasty side-effects with targets or other elements, then
I'll submit it as a patch post-0.85.
PS- no offense, but some of the code to initialise the project and
process the build file could us
Hi Pavan,
The simple answer is :
- follow this list
- find a bug in the bug database that you'd like to fix or
- implement some functionality that you think would be useful or has
been requested
- post any questions you might have here.
- post patches to the list
good luck.
Ian
Pavan B G wrote:
H
Gert Driesen wrote:
Hi,
In .NET 2.0 (beta 2), quite some options have been added to the command-line
compilers.
For example, for csc these are :
/keyfile:
/keycontainer:
/platform:
/reference:=
/langversion:
/pdb:
/moduleassemblyname:
Now, the question is: how do we expose these options to build a
Martin Aliger wrote:
Yes,
unfortunatelly NAnt do not accept types in nested blocks(like ,
etc.). There is pretty easy patch to enable that, which I sent to
list some time ago.
Gert, Ian, Scott - if you are interested in adding support for this, I'd
gladly make new patch against newest source
Gert Driesen wrote:
don't support the basedir property.
Ahh pity. From an academic, developer to developer point of view I'm
curious why that decision was made. I'm just wondering because
obviously that's a big decision since many existing Ant scripts use
${basedir} as a property and it
Hi Martin,
Martin Aliger wrote:
Thanks,
here is patch again, this time it is agains 0.85 RC3. I'd really love to see
this incorporated in core. There are some implementation problems which we
already discussed, though:
- what should happen, if referenced fileset have another basedir ?
- what
Ed Atwell wrote:
Hello all,
I was hoping to start contributing to NAnt by working on the bug list.
Are there any recommendations as to where I should start?
I'd suggest going after whatever looks easiest so that you can get a
feel for how the codebase is laid out. Pick one you like the look
Matt Trentini wrote:
Heya folks,
I've written a few NAnt custom tasks (some of which I want to roll
into NAntContrib) and I'd like to generate documentation for them in
the NAnt format.
How do I do that?
I've trawled the mail archives and various parts of the source code
but I can't seem to f
Martin Aliger wrote:
Or, alternativelly, it should not be hard at all to write task
just as a wrapper around msbuild.exe as ccnet do it. Something like
already do. Not bad idea. What others think about this? Maybe I'd not give
up mine hard-earned build scripts after all :-)
I think thats
Gert Driesen wrote:
-Original Message-
From: Martin Aliger [mailto:[EMAIL PROTECTED]
Sent: Monday, December 5, 2005 02:19 PM
To: ''Gert Driesen'', ''Ian MacLean''
Cc: [EMAIL PROTECTED], ''! nant''
Subject: RE: [nant-dev] nee
but maybe initially going with a plain task could be
the way to go.
Ian
-Original Message-----
From: Ian MacLean [mailto:[EMAIL PROTECTED]
Sent: Monday, December 5, 2005 06:38 AM
To: 'Martin Aliger'
Cc: [EMAIL PROTECTED], '! nant'
Subject: Re: [nant-dev] need VS 2005 so
I just saw this on the wix dev list. They've decided to use NAnt as
their build tool - instead of msbuild or nmake. Its quite cool to see
this - considering that the wix dev lead is at Microsoft. Interestingly
- NAnts support for the c++ compiler was one of the main reasons for the
decision.
Martin Aliger wrote:
I don't think we need to make task compatibility a
goal here.
I was thinking same, but first I wanted to use msbuild, I found myself in
situation where is used today. Even that msbuild is quite general
system, we, nant users, will call it mainly to compile vs2005 so
Hi Martin,
Sorry for the slow response to this
Martin Aliger wrote:
This introduce new boolean flag, which disable error message when XmlPeek
task coudn'd find any maching node. This is very useful in some scenarios.
I think, it could be useful to community, se here it is.
Thanks for the
Jason Diamond wrote:
>
>of functionality) but assuming that the NAnt output was fixed, it shouldn't
>be too hard to add support to SLiNgshoT to the round trip from .sln to
>.build and back to .sln again if you wanted to.
>
that would be pretty cool. Maybe you would need to have a seperate nant
>
>
>
>I'll try to take a look at what SLiNgshoT outputs (I've long since
>forgotten) to start generating some discussion on this. Maybe we could even
>make a VS.NET Custom Tool (like Chris Sells' CollectionGen) that can
>generate the .build file. The latest version of SLiNgshoT is broken up into
Chris Sells just released a tool for auto-generating type safe
collections from an xml based spec. This tool can plugs into visual
studio.NET and is pretty useful. So I've written a NAnt task for it. No
unit tests yet but I'm working on them.
See http://www.sellsbrothers.com/tools/#collectionG
Scott Hernandez wrote:
> I don?t know much about the development history so this may be a dumb
> question.
>
> Is there a reason that BuildElementAttribute isn?t derived from
> ElementNameAttribute.
>
Yes. they are performing different tasks. ElementNameAttribute is used
to associate an xml el
Gerry Shaw wrote:
>I suggested it as a task for the following reasons:
>
>* You can't auto build a schema until are the tasks are loaded.
>
Is this really true ? Can't we determine all tasks that would be
available to a NAnt build without actually running a build ?
>* The build file might conta
Scott Hernandez wrote:
>Agreed. This was one of the first things that I dislike about xml files
>that don't create xsds! Not only that, but type checking should be done
>before/as the document is used.
>
>I also think I can get support for ValidatorAttribute(s). We may need to
>add a static prope
Scott Hernandez wrote:
>I had imagined a collection of task-based schema definition files,
>probably just one for the core tasks, which would be combined at
>run-time to create the full schema definition. This way you could
>include as many as you like, or customize them.
>
>Automatic generation
Scott Hernandez wrote:
>Yeah, I'm not so sure this should cause an error. I'd be naturally
>inclined to go with it; thinking that if it isn't part of the task,
>leave it alone.
>
>Checking for required values is important. The one thing that the XSD
>won't do is check for required elements. It w
Bernard Vander Beken wrote:
>I agree with simplifying this.
>
>A note about the examples: the 'HelloWindowsForms' example is broken, is
>there a VB.NET developer who can take a look at it?
>
>Thanks,
>
+1 for me. I've found the multiple basedir specifications a bit confusing.
Ian
>
>
>Bernard
>
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 choos
Scott Hernandez wrote:
> Attached is sample of the output for tasks I am generating. I?ve been
> fighting with vs.net to get it working in the xml editor. It turns out
> the more normalized format I started with was giving no help in the
> vs.net xml editor. So I had to start over. This versio
Scott Hernandez wrote:
>So I did this (sent the email), then realized that if actually use the
>existing file (meaning you add an xmlns=" to the project element) it
>will cause problems with xpath queries.
>
>Before you actually build (use the build file) you need to remove the
>default namespac
Scott Hernandez wrote:
>>From a user's point of view (those writing the build files) we don't
>need to require that at all. Internally we could just add the namespace
>as we open the document. Then, as long as we use the prefix everywhere
>in code, it will work just fine.
>
>I'm still working on
[EMAIL PROTECTED] wrote:
>I downloaded the daily build and executed "bin\nant doc" and this failed.
>I'm using VS.NET Enterprise Architect Edition
>I don't know what other information would be usefull
>
Robert this is a known issue. What you can do is delete or move
collectiongen.dll from the bi
//throw exception!
> else
> ElementNames.Add(name);
>
> _name = name;
>}
>
>
>Or am I missing something about the design here?
>
>-Original Message-
>From: [EMAIL PROTECTED]
>[mailto:[EMAIL PROTECTED]] On Behalf Of Ian
>MacLean
>Sent:
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 t
Scott Hernandez wrote:
>
>>
>
>What about following the xml serialization standard and call them
>XmlAttributeAttribute and XmlElementAttribute? We could even set them as
>derived classes of the serialization ones.
>
I thought about this. Do we get any benefit from deriving from the
serializatio
Nathan Sharfi wrote:
>I thought the existing nant documentation was lacking, and also wanted to
>increase my xsl-fu. Hence, I'm converting the existing documentation to XML
>and using XSL to get html files. as you can see, I don't use MS' msxsl
>command-line util; I use one that's available from
Nathan Sharfi wrote:
>I thought the existing nant documentation was lacking, a
>
Oh yes could you say exactly what you think the existing documentation
is lacking ? I'm not saying it isn't lacking somthing I just want to
hear your opinion
Ian
___
Brad Wilson wrote:
>Scott Hernandez wrote:
>
>>Instead there is a xslt file(xslt/projecthelp.xslt) defined to generate
>>the help you are talking about. In the xslt file there is xpath query
>>that digs up the description from targets and displays it. This xslt
>>doesn't use the classes at all :(
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
I've just committed a patched ndoc that doesn't stop on a
typeloadexception. So we've got doc and userdoc targets working again.
Nathan,
try nant userdoc and let me know how you find the results. I'm looking
at updating the web-site version also.
I'm getting a nunit WarningFail that looks li
Andy Smith wrote:
> This is one thing that's bothered me for a while...
>
>
>
> 1) compile to a dll
>
> 2) change the .build file
>
> 3) run nant
>
>
>
> I don't know what nant does to know whether it needs to recompile...
> but in this instance, it won't!
>
> I have to go in and "touch" at
Brad Wilson wrote:
>Ian MacLean wrote:
>
>>Agreed. The basic issue is that the C# task has no knowledge that the
>>build file has been changed. If we make it compare tstamps for the build
>>file against the binary that sould give us enough infomation to work
>
Nathan Sharfi wrote:
>Kaboom! perhaps I'll try again tomorrow. I downloaded the thing about five
>minutes earlier.
>
Try using the latest cvs version. It will always be more up to date than
the snapshots.
Ian
___
Nant-developers mailing list
[EMAIL
Robert,
I've checked this in. thanks a lot. As for the exception - I think that
the approach that you've taken is correct. I don't view the "File
already added " error as catastrophic. As long as the user is informed
it should be OK. I think a property for this might be overkill. We
already
Scott Hernandez wrote:
>Yeah, I was just thinking about this the other day.
>
>With the conversation about aliases, and paths and stuff, this seems
>like something we need.
>
>Should we follow the .Net config standard and used the .config file like
>ASP.Net? Then we can do the whole config inheri
Scott Hernandez wrote:
>
>Here are the basic problems with code attributes:
>
>1.) Not everything is defined with NAnt Attributes. Take a look at
>FileSet. The includes and excludes elements are read thought the
>InitializeElement(XmlNode elementNode) method.
>
>2.) BuildElementAttribute does not
>
>
>>Scott wrote
>>
>
>Is there some problem using the field/property name as the xml attribute
>name?
>
Yes. Properties by convention are defined as upper case whereas
element/attribute names we have decided to make lowercase. I don't have
a problem with using the XmlAttributeAttributes howeve
Scott Hernandez wrote:
> I want to bring this up as a topic of its own. We have discussed what
> the behavior of loading assemblies and custom tasks before, but I
> wanted to make sure there was consensus, and a clear understanding of
> how things work.
>
>
>
> Let me start by stating how it
Scott Hernandez wrote:
>
>I was imagining that we would probably scan both "." and "./Tasks". It
>would not seem crazy to me to have build specific tasks in the build
>file directory.
>
>Take for example this directory structure:
>
>myproject
> myproject.build
> tasks (custom)
> src
>src.b
Scott Hernandez wrote:
>I don't consider this overly negative, but I am curious what the build
>patterns are.
>
What do you mean by build patterns ??
>
>
>Anyway, I really don't care one way or another, I just think that at
>this point, without more user feedback, and comments, I don't see one
>
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
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]>
>
>
>H
Scott Hernandez wrote:
> When do these file get updated? I?d like to do an update to them soon
> based on the changes we?ve been making.
>
> Is there a process in place for this, or just build and update?
>
no process. They should be updated for every major checkin. Its a good
test that nant bu
Nathan Sharfi wrote:
>The Vb6 task seems to be a copy of Tlbimp's. Shouldn't it be removed?
>
It does what you'd think it does - ie run the vb6 compiler. However
you're right - the docs are pretty sketchy and need to be fixed
Ian
>__
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'
Jason wrote:
>I was just wondering how close the project is to a .8 release? I was reading
>the To Do file and was wondering how the progress was on these To Do's.
>
We don't have a fixed time for a 0.8 release. I would prefer to defer
that until Gerry gets back from his vacation.
>I was inte
[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?
[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?
s a good plan. Do you think we should move it into the nant
namespace ? NAnt.Util or somthing like that.
Ian
>
>- Original Message -
>From: "Ian MacLean" <[EMAIL PROTECTED]>
>To: "Jason Diamond" <[EMAIL PROTECTED]>
>Cc: <[EMAIL
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 be
ng tonight's build pretty much the
release if we are going for Friday.
-----Original Message-
From: Ian MacLean
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 maintena
Bernard Vander Beken wrote:
Hello,
I have attempted to complete the documentation for the VB6 task in CVS, but there are still some open items:
- The output attribute is currently required but what is it exact intention? I suggest making it optional or remove it.
- Two filesets a
wow,
this is awesome I was intending to work on the nunitreport stuff myself but
since you've already done such a great job. I'd like to drop this one into
the main cvs if you don't have any objections.
oh and a small typo. The site says "This is a set of NAnt that you can use" instead
201 - 300 of 661 matches
Mail list logo
