--
From:
Gert
Driesen
To: 'Jaroslaw Kowalski'
Cc: [EMAIL PROTECTED]
Sent: Sunday, December 19, 2004 1:40
PM
Subject: RE: NDoc 1.3
Hi Jarek,
I'm still in flux on how to proceed with this. Adding all
documenters (and their dependencies, which
I don't know exactly what you're trying to achieve with Gump, but IMO things
are much easier than you think if you fully utilize NAnt's potential.
Nant is quite a portable beast today. It can run on 4 platforms (mono-1.0,
net-1.0, net-1.1, net-2.0) and compile for some more (netcf-1.0 and sscli).
I think that you cannot avoid GAC with .NET because of the order in which
the assebmlies are located:
http://www.awprofessional.com/articles/article.asp?p=30601seqNum=6
The only way would be to remove all non-MS assemblies from it.
I may be wrong, though ;-)
Jarek
- Original Message
, Jaroslaw Kowalski [EMAIL PROTECTED] wrote:
I think that you cannot avoid GAC with .NET because of the order in
which the assebmlies are located:
http://www.awprofessional.com/articles/article.asp?p=30601seqNum=6
Thank you for that URL.
In Gump's case we probably can live with making
Hi Clayton!
What's wrong with using the NAnt-provided bootstrap procedure? It uses a
portable mini-nant that is stored in CVS can run on any platform supported.
You just do either:
bin/NAnt.exe
or
mono bin/NAnt.exe
and it will build the entire nant and put it into build/**/bin
If you want to
-
From: Adam R. B. Jack [EMAIL PROTECTED]
To: Clayton Harbour [EMAIL PROTECTED]; Jaroslaw Kowalski
[EMAIL PROTECTED]; [EMAIL PROTECTED];
[EMAIL PROTECTED]
Sent: Monday, September 06, 2004 10:16 PM
Subject: Re: [nant-dev] Re: NAnt
I was talking with Adam the other day and he suggested that a batch
This is ofcourse the best solution for the issue Jeroen brought up, but
that
other users might still expect the possibility to use relational
operations
on versions. Meaning: should the following functions return a version
data
type :
assembly::get-version(string)
Hi guys!
I'd like to propose the introduction of typed
properties to NAnt. Currently properties are stored as strings which has many
drawbacks, esp. when used within expressions.
For example:
property name="a" value="false"
/
if test="${a=false}"
...
/if
this test fails because:
1. "a"
My vote: let's NOT support it - I'd say more - let's disallow it. Simplicity
is an important thing.
The only advantage of XML namespaces I see is technical beauty and XSD
schema support for extensible intellisense - IMHO it's not worth it.
From my experience I can say that it's really difficult
which would just append the path based on the location of the package.
This
would be taken from AssemblyFolders on Windows and pkg-config or mono
packages on Linux.
Not sure in what way AssemblyFolder and pkg-config packages are related ?
They both provide a way to specify the location
;-) sorry
- Original Message -
From: Gert Driesen [EMAIL PROTECTED]
To: Jaroslaw Kowalski [EMAIL PROTECTED]; Giuseppe Greco
[EMAIL PROTECTED]; NAnt Developers
[EMAIL PROTECTED]
Sent: Thursday, May 20, 2004 7:30 PM
Subject: Re: [nant-dev] get-assembly-direcotry() function
We can have a null literal and overload comparisons for equality and
inequality:
if test=${property::get-value(...) != null} /
This would make 3 literals: true, false, null
Jarek
- Original Message -
From: Ian MacLean [EMAIL PROTECTED]
To: Gert Driesen [EMAIL PROTECTED]
Cc:
+1 for this idea.
Jarek
- Original Message -
From: Gert Driesen [EMAIL PROTECTED]
To: Ian MacLean [EMAIL PROTECTED]; John Cole [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Thursday, May 13, 2004 6:42 PM
Subject: AssemblyFileSet (was Re: [nant-dev] Custom Function to select from
ODBC
Unfortunately I get this:
=
NAnt 0.85 (Build 0.85.1592.0; mono-1.0.unix; nightly; 5/11/2004)
Copyright (C) 2001-2004 Gerry Shaw
NAnt Team
BUILD FAILED
The current runtime framework 'mono-1.0' is not correctly configured in the
NAnt configuration file.
The 'System.dll' assembly does
Yes, I committed a mono patch that fixes the encoding issue. You can try it
from mono/cvs.
Jarek
- Original Message -
From: Ian MacLean [EMAIL PROTECTED]
To: Gert Driesen [EMAIL PROTECTED]
Cc: Jaroslaw Kowalski [EMAIL PROTECTED]; Nant-Developers (E-Mail)
[EMAIL PROTECTED]
Sent: Tuesday
[EMAIL PROTECTED]
To: Jaroslaw Kowalski [EMAIL PROTECTED]
Cc: Nicklas Norling [EMAIL PROTECTED]; Nant-Developers (E-mail)
[EMAIL PROTECTED]
Sent: Wednesday, March 24, 2004 11:44 AM
Subject: Re: [nant-dev] Windows setup contribution
Why not just add an install target to nant.build and have
Very nice installer!
I have some ideas for 1.0 release and I wonder if they can all be
implemented with this tool:
1. Binaries should go to Program Files\NAnt\bin and should include *.exe,
*.dll but no *.xml (at least not by default)
2. I wonder if we could get rid of the *.pdb since they
Can you try the latest nightly build? Many, many solution bugs were fixed
since then.
Jarek
- Original Message -
From: Greg Arzoomanian [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, March 16, 2004 5:34 PM
Subject: [nant-dev] Bug report
I'm receiving the following message
for more details.
//
// You should have received a copy of the GNU General Public License
// along with this program; if not, write to the Free Software
// Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
//
// Ian Maclean ([EMAIL PROTECTED])
// Jaroslaw Kowalski ([EMAIL
this for arrays of properties.
This concatenation could be done for any Collection that could be
enumerated.
Is this the case for filesets?
Two cents,
Peter
-Original Message-
From: Jaroslaw Kowalski [mailto:[EMAIL PROTECTED]
Sent: Friday, March 19, 2004 10:24 AM
To: [EMAIL PROTECTED
3. does nant support building C?
Just ask it to the NAnt community: Ian, Gert, Jarek, is there any
plan to build C support in NAnt?
I don't think it's a good idea for NAnt to directly support C compilation or
even C compiler invocation, just because it's s complex (just look at
the size
Perhaps we could have a webdav-copy task instead that would be similar to
copy but accept WebDAV sources/targets.
+1 for the idea of removing WebDAV from the solution task.
Jarek
- Original Message -
From: Erick Thompson [EMAIL PROTECTED]
To: Gert Driesen [EMAIL PROTECTED]; NAnt Users
Hi Alex!
Just out of curiosity: I remember MSBuild used to have a syntax where you
had to use Task name=... ... / to run tasks.
In your example I see MakeDir, Touch, Delete
What version of the syntax are you going to support in Whidbey?
Jarek
- Original Message -
From: Alex Kipman
Good point. I've just comitted a two-line patch that adds
Excludes.Add(**/.svn);
Excludes.Add(**/.svn/**);
Jarek
BTW. Subversion rocks!!! I've been using it since 0.37 and it works great.
No more directory versioning/file rename problems,
- Original Message -
From: Giuseppe Greco
Ian, Gert, and Jarek, don't you think that the
svn task should be placed in the NAnt core?
If it's stable enough (I don't see why it would be 'unstable' - it's just a
wrapper), +1 to this idea.
Jarek
---
This SF.Net email is sponsored by:
This is related to a bug in mono. I've reported it as a bug in ximian
bugzilla.
http://bugzilla.ximian.com/show_bug.cgi?id=54980
Note that NUnit is not working either.
I hacked mcs with this patch:
---
Index: System/AppDomain.cs
If it happens on Unix - add mcs/csc to your PATH.
On Windows - you need to have .NET 1.0 installed in order for solution to
work. This will be sorted out in the future.
Jarek
- Original Message -
From: Ladva, Hitesh [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, March 02, 2004
This patch adds wildcard support to file::exists(). Basically it uses
DirectoryScanner to find matching files.
Is it ok to commit it ?
Jarek
fileexists.patch
Description: Binary data
Speed? Of course it's possible to always use the scanner and I can change
it.
Jarek
- Original Message -
From: Scott Hernandez [EMAIL PROTECTED]
To: Jaroslaw Kowalski [EMAIL PROTECTED]; Hemry, Jeff
[EMAIL PROTECTED]
Cc: ! nant [EMAIL PROTECTED]
Sent: Friday, February 27, 2004 8:27 PM
Yeah, I'm sure we all go back and forward on this issue. Performance is
important, and we should strive towards it, but I have found that
sometimes
what seems like a performance tweak turns out to not work out as I expect.
I'm sure the scanner is slower than file.exists, but in this case I
2) Availabletask: modified to allow for wildcards, such that it would be
acceptable to determine if c:\temp\*.txt is available.
I guess you could accomplish this using the foreach task, perhaps not a
pretty way to do it, but possible ...
We are actually thinking about deprecating the
Hi!
I've prepared a nant patch that adds support for datetime and timespan
literals in expressions.
This is a first step towards improving implicit vs explicit conversions
issue. Today, the only way to specify a date literal is to use:
convert::to-datetime(MM/DD/) which is not very elegant.
We (I added this recently) currently also allow an implicit conversion of
null to a (empty) string, which is useful for functions that return
reference types (eg. framework::get-runtime-engine()). Should we keep
this,
or do you want to add a is-null() function (in what namespace) and a
you really want to allow the cultures to be specified? Why? This kills
portability IMHO.
Again, I agree that this is not very readably, but I think this is a
problem
with the expression support as such ...
;-( What can we do to improve it?
Jarek
- Original Message -
From: Jaroslaw
This may be related to some mono bug, but I'm no longer able to run NAnt on
linux.
I get:
System.NullReferenceException: A null value was found where an object
instance was required
in 0x00068 NAnt.Core.DirectoryScanner:ParseSearchDirectoryAndPattern
(string,string,bool,string)
in 0x000a2
Oh - we already mention it before. Would be great! And also + operator in
expressions could be overriden to fileset merge :) And functions with
fileset argument could exists instead of string as refid to fileset etc
etc
etc...
The overload is a bad idea. Currently it has problems with strings
I already asked Jarek to correct the permissions (or just remove all files
and directories in nightly/help altogether), but he hasn't responded yet
...
The permissions set by the nightly build process should be ok, so I assume
Jarek manually set the permissions ...
Sorry Gert, I didn't know
Perhaps it would be more efficient to hold off on the patch until more
people have provided feedback, and until we've decided it in more detail.
I'd hate to see your efforts go to waste ...
My 0.02 PLN:
1. I don't think merging can be done in a generic way (neither on xml level
nor at the
BTW. Can you have this? (both reference a named fileset and re-define it ?)
fileset id=aaa refid=aaa
includes name=*.* /
/fileset
Jarek
---
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development
Not in current implementation. I dont like it much - using both id and
refid
is little opaque...
Better to introduce what you suggest in previous mail:
fileset id=aaa
includes refid=aaa /
includes name=*.* /
/fileset
To be more readable, I would:
1. Make fileset fail on attempts
I think this is sufficient in 99.9% scenarios so if we don't find merge be
useful we could always implement this [I have it in some state already]
Should such implementation include even excludes from referenced fileset?
I suggest the following evaluation semantics:
fileset
includes
I think this is sufficient in 99.9% scenarios so if we don't find merge be
useful we could always implement this [I have it in some state already]
Should such implementation include even excludes from referenced fileset?
I suggest the following evaluation semantics:
fileset
includes
Sorry for my previous example. The resulting fileset should be empty because
files cannot be both xxx.* and AAA.*.
Jarek
the resulting fileset is (in terms of the set algebra, + means union, -
means difference)
L1 + L2 - (L3 - L4)
so (because we're excluding almost every file but AAA.*)
You mean the same task used for cleaning? Why?
csc output=... buildmode=clean
/csc
Jarek
I don't mind, but we should perhaps consider having a buildmode or
something, which can be set to Build (default), Rebuild, Clean,
Gert
---
, 2004 9:39 PM
Subject: RE: [nant-dev] Bug #875664
Gert/All,
Jaroslaw Kowalski, has contacted me off list and we are working to resolve
this issue.
Thanks
-Mark
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 13, 2004 15:25
To: Mark
Hi Giuseppe!
Are there also changes related to the uptodate task?
The following fragment doesn't work anymore:
uptodate
targetfile=figures/project-structure.gif
sourcefile=${build.dir}/figures/project-structure.xcf
property=project-structure.gif.uptodate/
ifnot
expression support sounds like a must, no? Somehow I thought our
expression engine already supported this.
- Original Message -
From: Jaroslaw Kowalski [EMAIL PROTECTED]
[snip]
BTW. Gert, what do you think about allowing sub-expression evaluation in
strings so that we could write
OK - I think we can do without the definefunctions attribute though.
I'll just make the implicit script class a FunctionSet behind the scenes
and remove the constraint that you have to have a ScriptMain.
What about the namespace?
Jarek
I think add the namespace attribute but make it non-required. Just the
global namespace if its present. Since none of the built-in functions
reside in the global namespace that shouldn't be a problem.
I'm afraid there's no global namespace ;-( And parser does rely on the fact
that every
that is
straighforward. Just override method MergeWith (defined in BaseType).
Base
method just throws BuildException.
Martin
- Original Message -
From: Ian MacLean [EMAIL PROTECTED]
To: Jaroslaw Kowalski [EMAIL PROTECTED]
Cc: Martin Aliger [EMAIL PROTECTED]; ! nant
[EMAIL
Nice.
I also though about it some time ago. Wouldn't it be cleaner to write it
like the following?
script language=C# definefunctions=true namespace=test
[Function(test-func)]
public string Testfunc( ) {
return some result ;
}
/script
Most parts of the script code
script language=C# function=Testfunc
return some result ;
/script
That can't be done because you need the type information for formal
parameters and returned value.
Jarek
---
This SF.net email is sponsored by: Perforce
- Original Message -
From: Tim Dallmann [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, January 07, 2004 8:49 PM
Subject: [nant-dev] can't post a problem to this list
Hi,
I keep getting the following message every time I try to post an error to
this forum:
You message
Some time ago I proposed a syntax to allow the ultimate customization of
solution task.
It was something like:
solution configuration=Release outputdir=${output.dir}
includevsfolders=false showcommands=true
projects
includes name=${build.dir}/**/*.csproj/
/projects
override
How about a modify-fileset task? Like this:
modify-fileset id=f1 mode=add | delete | replace
fileset
/fileset
/modify
It would take either replace the f1 with the contents of fileset, add
new items or delete matching items.
Jarek
- Original Message -
From: Martin Aliger [EMAIL
Ok. Unfortunately I'm using VS.NET 2003 so I'll add it by hand to the CSPROJ
file. Not sure if this won't break things.
Jarek
- Original Message -
From: Gert Driesen [EMAIL PROTECTED]
To: Jaroslaw Kowalski [EMAIL PROTECTED]; Scott Hernandez
[EMAIL PROTECTED]; ! nant [EMAIL PROTECTED
Hi!
As Mono is progressing towards 1.0, I think we should start thinking about a
binary distribution of NAnt that would run unmodified on all CLI platforms.
I've done some review of the NAnt source code and looks like there are no
fundamental problems that would prevent us from achieving this
Hi!
I've noticed that nantschema task is broken, so I sat down and fixed it
(Scott - I hope you don't mind ;-).
I've attached the result of my work for you to review.
Changes/new features:
1. Basically I've rewritten most of NAntSchemaGenerator, simplified the code
and removed unused
Hi guys!
I've juest committed two new fundamentals pages regarding Expressions and
Functions.
I'm not a native English speaker, and I don't feel my English is good enough
to write documentation. Can someone take a look at the files and fix
grammar/spelling errors?
Jarek
3/
I'm also thinking about fileset support. Could be possible to extend
relation between tasks/types/functions? I mean, many tasks now use
filesets.
What about functions? Could be nice in some cases... E.g.:
fileset id='f1'!-- define fileset --
includeList ...
/fileset
...
foreach
BTW. Expression support is in the latest daily build, so you should be able
to try it out. It's also in CVS HEAD now. You can play with functions and
fileset support. It could be an interesting addition to NAnt.
Jarek
- Original Message -
From: Jaroslaw Kowalski [EMAIL PROTECTED
Hi Matt.
Can you please check that it's not expression evaluator that's causing the
problem (it was recently added to CVS/nightly build). There's a new option
disable-ee that can be used to revert to the old behaviour.
Jarek
- Original Message -
From: Matthew Mastracci [EMAIL
We already have tasks:
sysinfo
tstamp
available
if
that are basically readonly (they only change properties) and are just used
to retrieve/calculate some information. We have four ways of doing so, why
add fifth one? I think this should be done as a function ONLY:
property name=somepath
Tasks should offer functionality on a much higher level than functions ...
Here's my dream about NAnt:
1. Tasks should actually DO something. That something is: compile, create,
delete, XSL transform, update from cvs, send email, run unit tests, install,
uninstall, start/stop services,
Should I add Deprecated attribute to propertyexists, propertytrue and
taskexists in EE-patches?
Jarek
- Original Message -
From: Ian MacLean [EMAIL PROTECTED]
To: Jaroslaw Kowalski [EMAIL PROTECTED]
Cc: Gert Driesen [EMAIL PROTECTED]; William E Caputo
[EMAIL PROTECTED]; Nant-Developers
Ok. Should we do something with uptodatefile before the merge? If we do so,
we can deprecate ifnot as well.
Jarek
- Original Message -
From: Ian MacLean [EMAIL PROTECTED]
To: Jaroslaw Kowalski [EMAIL PROTECTED]
Cc: Gert Driesen [EMAIL PROTECTED]; William E Caputo
[EMAIL PROTECTED]; Nant
PS. Sorry if I sometimes sound negative about expression support ... I
really like and appreciate what you've done so far, but I just want to be
sure we're doing the right thing and not let you guys get carried away in
your enthousiasm too fast :-) But I agree that its really exciting
Hi!
Quick Summary: This message discusses changes that are going to be made to
NAnt, which may break your build files in future releases. Before we make
it, we'd like to hear your opinion on the subject
As you may know, there's an ongoing effort to implement expression evaluator
for NAnt. We'll
The next thing I'll look at is namespace support which would be somthing
like :
[CustomFunctionSet(NameSpaceUri=somenamespace, prefix=foo )]
I suggest, that we included something like a category/description which
would be used to generate
the documentation.
-
From: Ian MacLean [EMAIL PROTECTED]
Cc: Jaroslaw Kowalski [EMAIL PROTECTED];
[EMAIL PROTECTED]
Sent: Wednesday, December 10, 2003 3:30 PM
Subject: Re: [nant-dev] Naming of documentation files
Good work on the userdoc stuff for functions Jarek. I just built after
syncing your checkins. It looks
I'll add the category stuff.
BTW. How to do select-distinct in XPath ?
Jarek
- Original Message -
From: Ian MacLean [EMAIL PROTECTED]
To: Jaroslaw Kowalski [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Wednesday, December 10, 2003 4:02 PM
Subject: Re: [nant-dev] Naming of documentation
))
- anything will NEVER be evaluated because we know that it's value is
irrelevant
What do you think?
Jarek
- Original Message -
From: Jaroslaw Kowalski [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, December 10, 2003 8:35 PM
Subject: [nant-dev] Function index now splitted by category
Ian,
I've committed some changes to EE - mostly cleanup and refactoring.
There's a TODO in ExpressionEvalBase.cs - can you please take a look at it
and tell me how to emit a deprecated warning?
Jarek
- Original Message -
From: Ian MacLean [EMAIL PROTECTED]
To: Jaroslaw Kowalski [EMAIL
I'm forwarding your question to nant-developers mailing list where Ian is
taking care of loading custom expressions.
Jarek
BTW. I've added LastIndexOf to the core functions in EE as it is generally
useful. It's now in CVS.
- Original Message -
From: Arif Mohammed [EMAIL PROTECTED]
To:
Hi!
Is there any reason why filenames in NAnt
help/website are named like this:
fog06.htmlfog13.htmlfog40.htmlfog41.htmlfog42.htmlfog79.htmlfog81.html
I'd like to add a section on expressions and
functions. How should I name the
to document Tasks and Types (from source
code xml comments). The rest of the docs are created from the xhtml in the
doc folder.
- Original Message -
From: Jaroslaw Kowalski
To: [EMAIL PROTECTED]
Sent: Tuesday, December 09, 2003 6:07 AM
Subject: [nant-dev] Naming
As my previous e-mail bounced because it was too big (41 KB 40KB limit!)
I'm resending this to the list without the patch.
Again, I encourage everyone to download and try test2 and share your
opinion.
Jarek
- Original Message -
From: Jaroslaw Kowalski [EMAIL PROTECTED]
To: [EMAIL
OK. Committed.
Jarek
- Original Message -
From: Ian MacLean [EMAIL PROTECTED]
To: Jaroslaw Kowalski [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Monday, December 08, 2003 9:23 AM
Subject: Re: [nant-dev] Fw: Expression evaluator changes
Could you just commit to the branch ? I'd like
[EMAIL PROTECTED]
To: Jaroslaw Kowalski [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Monday, December 08, 2003 9:35 AM
Subject: Re: [nant-dev] Fw: Expression evaluator changes
Awesome, thanks !
Ian
Jaroslaw Kowalski wrote:
OK. Committed.
Jarek
- Original Message -
From: Ian
Do you think the functions need to be defined as static ? I was thinking
of making them public instance and passing a Project instance to the
containing objects constructor so that functions can have access to
various information inside the project - the same as tasks can now. It
might be
Hi,
what I think about dash problem:
- in writing xml element names (Nant tasks) is common to use dashes
Agreed.
I see 2 possible way how to enable use of properties (and even
functions)
with dash in name:
A/ allow it on lexical level:
So: if test=${some-long-property -
Hi Martin,
I reconsidered your arguments for lexical separation, and I tend to think
that this might be a way to go during the transition period.
A/ allow it on lexical level:
So: if test=${some-long-property - long-function(1)=42}/ it means
prop - func(1)=42
but if
Thanks for your opinion Scott.
Now for the larger question, Does everyone want expression support in
NAnt?
I think there are some real benefits to adding expression support. It will
make things much more flexible. But it also means that more complicated
and
possibly harder to read build
By adding expression support we are moving functionality from the tasks
(defined by xml) to the expression engine. Now I am starting to think
about
how to add support for extensions to the expression engine; just like I
think about how to add functionality by creating new tasks. This is the
Good point about side-effects. This does paint a clear distinction. But
then
you get tasks like xmlpoke, with no corresponding xmlpeek; this might make
the user search around for the expression/function to use, or even assume
that this functionality does not exist.
You're right. Perhaps
') instead of
nant.tasks.TASKNAME.location. Assuming this, there would be no need to
have properties with dashes in them.
Jarek
- Original Message -
From: Gert Driesen [EMAIL PROTECTED]
To: Jaroslaw Kowalski [EMAIL PROTECTED]; Ian MacLean
[EMAIL PROTECTED]; Martin Aliger [EMAIL PROTECTED]
Cc
I'll do it when I manage to re-format the code. Unfortunately NAnt coding
style is a bit different than mine. I'm fighting with astyle right now ;-)
Jarek
- Original Message -
From: Ian MacLean [EMAIL PROTECTED]
To: Jaroslaw Kowalski [EMAIL PROTECTED]
Cc: Martin Aliger [EMAIL PROTECTED
and contains only
letters, digits underscores or dashes.
This may affect people using property names with non-latin characters.
Jarek
- Original Message -
From: Ian MacLean [EMAIL PROTECTED]
To: Martin Aliger [EMAIL PROTECTED]
Cc: Jaroslaw Kowalski [EMAIL PROTECTED]; Gert Driesen
[EMAIL
be written as
if test=${...} /
just for the consistency.
Jarek
- Original Message -
From: Martin Aliger [EMAIL PROTECTED]
To: Gert Driesen [EMAIL PROTECTED]; Ian MacLean
[EMAIL PROTECTED]
Cc: Jaroslaw Kowalski [EMAIL PROTECTED];
[EMAIL PROTECTED]
Sent: Wednesday, December 03, 2003 3:50 PM
Hi!
I've committed expression evaluator (as in test1 release) to CVS in
EE-patches branch.
I think what we now need is:
- unit tests (for ExpressionEval classes alone as they are easily separable
and for NAnt changes.
- user documentation
Unfortunately these tasks cannot be started until we
.).
For strings, I'm planning to provide embedded expressions, like:
echo message=the length of the file is: %{filelength(${filename})} /
What do you think?
Jarek
- Original Message -
From: Martin Aliger [EMAIL PROTECTED]
To: Ian MacLean [EMAIL PROTECTED]; Jaroslaw Kowalski
[EMAIL PROTECTED]
Cc
operators be and, or or ||, (amp;amp;) in
XML)
I'm awaiting your opinions.
Jarek
- Original Message -
From: Martin Aliger [EMAIL PROTECTED]
To: Jaroslaw Kowalski [EMAIL PROTECTED]; Ian MacLean
[EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Tuesday, December 02, 2003 3:44 PM
Subject: Re: [nant
But it may break some build scripts which use length and similar
keywords
as property names. What should we do then?
true :-( Looks we couldn't be 100% compatible... Unless expression
generator
allows to use length variable/property and length() function in the
same
time.
It's of course
Hi!
Here's the first test release of the expression evaluator I'm developing for
NAnt.
I encourage everyone to try it. I'd like to get as much feedback as possible
on it.
Please report:
1. Does it work for you? Bug reports are welcome.
2. Is it useful?
3. Do you find the syntax simple enough?
Hi!
According to releaseplan.html a "Move to an Apache or
BSD-style license." is planned for 0.9. As I'm going to contribute some code to
NAnt (_expression_ evaluator) I have a concern: I'd like my code to be BSD-licensed. Do I need
to do anything special to be GPL-compatible? Is it ok if I
Hi!
As I've promised some time ago on the list, I've implemented a simple, yet
very powerful, expression evaluator for NAnt. See below for a full list of
features.
You can now write quite sophisticated expressions, like:
if test=tolower(${somefilename}) = ${someotherfilename} + '.txt'
...
/if
Can't you just use the binaries from .NET 1.0 on Mono, too ?
You could just ignore some tasks, and it should be fine...
Jarek
- Original Message -
From: Scott Hernandez [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, November 07, 2003 6:21 AM
Subject: RE: [nant-dev] Criteria for
You can use my trick:
The technique consists of:
1. A plain text file that holds nothing but a version number
AA.BB.CC.DD (version.txt)
2. A small C# utility that increments one of the components in
the file (NewBuild.exe)
3.A small C# utility that replaces AssemblyVersion(...)
in all
Title: Message
Yes, it seems to be legal: a snapshot of my
ILDASM dump:
.assembly extern Sooda{
.publickeytoken = (36 D3 1D A5 0D 00 DE DD
)
// 6... .ver 1234:1234:1234:5}
Jarek
- Original Message -
From:
Anthony LoveFrancisco
To: 'Jaroslaw Kowalski
ecode which requires a rather complicated autoconf/Makefile stuff
+ a C compiler.
Jarek
P.S. I like "awk" very much,
though.
- Original Message -
From:
Anthony LoveFrancisco
To: 'Jaroslaw Kowalski' ; 'Daniel Nguyen' ; [EMAIL PROTECTED]
; [EMAIL PROTECTED]
Sent:
1 - 100 of 121 matches
Mail list logo
