Thanks for the compliments. The tool wouldn't be where it is today
without the contributions of everybody that has worked on the project.
I'm forwarding this to the nant-dev list as they deserve the thanks
more than I do. As you know yourself by working on an open source
project, a project
Thanks Sean, in the future send these types of email to the nant-dev
list.
On 18-Dec-03, at 11:43 AM, Foy, Sean wrote:
I recently found that NAnt could not build one of my solutions using
the
solution task and, finding nothing in the bugs database, decided to do
something about it.
My project
Bah, reply strips attachments... Here is the attachment for the fix
from Sean Foy.
nant-interop-fix.zip
Description: Zip archive
On Thu, 13 Mar 2003, Arjen Poutsma wrote:
I've already created such a regex task, which sets properties based on named Groups
(?name).
For example, for the regular expression ^(?name\w+):(?value\w+), you'd say:
regex pattern=^(?lt;name\w+):(?lt;value\w+) input=Section1:119900/
echo
On Wednesday, February 19, 2003, at 10:17 AM,
[EMAIL PROTECTED] wrote:
Gerry:
delete dir=f00/
The delete task will not raise an error and your directory foo will
not
exist.
I liked the feature that Gert suggested, but I see Gerry's point. What
about this:
Add an attribute, say
If this process is reliable then I suggest we remove the nightly
snapshots.
+1
---
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
I've discarded over 100 emails from the list in last 36 hours because of
some spamming. If I've accidentally discarded a legit email please send
it again cc'ing directly to me.
At least mailman was good enough to block some of the spam.
---
Use the sysinfo task.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of Kevin
Miller
Sent: October 3, 2002 11:36 AM
To: Nant-Developers (E-mail)
Subject: [nant-dev] Environment Task
Am I missing something. Is there a task that will let me retrieve
to be
replaced or spun off as a separate project. I just whipped it up as an
example of nant was designed to be used.
-Original Message-
From: Brian Ritchie
To: Gerry Shaw
Sent: Wed, June 26, 2002 11:00 AM
Subject: NAnt Patch
I'm not sure if you're the right one to send this to, so let me know if
I
Can you help the slower people in the group by explaining a bit more
about the foreach task. I can see how it could print out all the
properties
* What do you plan on doing with it?
* What is the syntax for iterating over the containers?
* What containers can you iterate over? properites,
I'm in favor on the config stuff for defining how tasks run. The
complier tasks beg for this feature.
I'm not sure why we need case insensitivity in filesets. Is it really
that hard to write the paths with the correct case? If I'm missing
something please bring it up. If its really a big
What do people think of this? IMO the neseted properties for the nant
task seems to fall into line with the concept of Tomas's optionset idea.
-Original Message-
From: Mark Griffiths [mailto:[EMAIL PROTECTED]]
Sent: Mon, June 24, 2002 2:32 AM
To: Gerry Shaw
Subject: RE: NAntTask Patch
solving your problem this way rather than
the comma seperated include pattern.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On
Behalf Of Kevin Dente
Sent: Sun, June 23, 2002 6:12 PM
To: Gerry Shaw; 'Nant developer's list'
Subject: RE: [nant-dev] FileSet
There isn't specially setup for this. This hack seems pretty
reasonably to me. At least it doesn't require any special conditions to
be added to nant to have it work.
Master.build
property name=called-from-master value=true/
nant buildfile=Child.build inheritall=true/
I was thinking about the id'ed FileSet's. Here is what would need
changing:
* Add an Id property to the FileSet class
I'm kind of curious about why implement it this way it
seems to me, that everything in the buildfile should be able
to be referenced by an ID, so I'd think a
The docs are wrong. I shamelessly compied from directly from Ant :) and
I must have missed that.
I'm not sure it adds anything that you could already do with multiple
include tags. I perfer things to be really obvious at the expense of
more typing since you only have type stuff once but it
Has anybody looked at adding the id/idref of Ant to
NAnt? It's looking to me like very useful feature.
On paper (I have never used it) this features sounds pretty cool. I
think it would be a great contribution to have but might be tricky to
code. It would require changes to the nant.core so
Great list Scott! Here is a somewhat subjective ranking of them:
Easy and important:
Call
Copy
Delete
Echo
Fail
Mkdir
Move
Property
Hard but important:
Ndoc
Script
Sleep
Style
Zip
Not as important (non-core tasks):
Al
Cl
Gac
Mcs
Rc
Tlbexp
Typedcollection
-Original Message-
From:
Which is why the offer still stands that if anybody has an ASP.NET
server that they would like to denote as the official nant build server
I'd be happy to help them set it up. The build server would watch cvs
and do builds anytime a commit is made and send out an email on the
result.
Right, I
Seeing how we already have nant.filename I can't really see the harm in
also adding a nant.home environment variable that would do what Tomas
wants.
You can see the list of variables that nant is suppose to define here:
http://nant.sourceforge.net/help/fundamentals/fog82.html
Also to
no end of trouble
(and are once again broken).
-Original Message-
From: Bernard Vander Beken [mailto:[EMAIL PROTECTED]]
Sent: Tue, April 16, 2002 3:55 AM
To: Gerry Shaw
Subject: RE: NAnt bug : BaseDirectory problems in NantTask.cs
AND/OR Project.cs
Thanks, but this does
/Parent.build
nant - subdir/Child.build
What will be the basedir for the child.build Project? (/subdir/ or /)
Assuming you what you meant by your notation means:
Parent.build
project
nant buildfile=subdir/Child.build/
/project
The basedir of the child.build would be the same as
22 matches
Mail list logo
