Re: [nant-dev] ?
On Sat, 2004-01-10 at 15:50, Gert Driesen wrote:
Gert thanks,
Giuseppe,
Expression support is still very much alpha, so indeed things have changed
since the initial implementation
About the resgen task : I don't have access to NAnt sources right now (and
sf is down for maintenance), but it could be that you should now also
specify the path information in the output attribute,
OK, that works fine.
and that the todir attribute is now only used in combination with the
resources fileset as it makes more sense to specify both the
path and filename in the output attribute when dealing with a single
input file. I'd have to check the sources to be sure of that, but
I think I did make some changes to that ...
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 test=${project-structure.gif.uptodate}
exec
program=xcftoall
commandline=
--gif --output=${build.dir}/figures/image.gif figures/image.xcf/
/ifnot
the uptodate/ifnot task pair causes the following exception:
INTERNAL ERROR
System.NullReferenceException: A null value was found where an object
instance was required
in 0x00244 NAnt.Core.Task:Execute ()
in 0x002a3 NAnt.Core.Target:Execute ()
in 0x000d8 NAnt.Core.Project:Execute (string,bool)
in 0x0030d NAnt.Core.Project:Execute ()
in 0x00185 NAnt.Core.Project:Run ()
Gius_.
Gert
- Original Message - t
From: Giuseppe Greco [EMAIL PROTECTED]
To: NAnt Developers [EMAIL PROTECTED]
Sent: Saturday, January 10, 2004 2:18 PM
Subject: [nant-dev] ?
Hi all,
I've checked out the latest version of NAnt from
cvs, and I've noted some differences...
For example,
ifnot test=${nant::property-exists('configured')}
...
/ifnot
is not longer valid; instead, one has to specify something
like this:
ifnot test=${property::exists('configured')}
...
/ifnot
Ok, that's easy... but what's about the following target?
target
name=build-resources
description=Builds resource binaries
foreach
item=String
in=de-DE,en-US,es-ES,fr-FR,it-IT
delim=,
property=culture
mkdir
dir=${build.dir}/${package.name}/lib/${culture}
failonerror=false/
resgen
input=${module}.${culture}.resx
output=${module}.${culture}.resources
todir=${build.dir}/${package.name}/lib/${culture}/
/foreach
/target
The target above worked fine before the updated. Now, it just
creates the directories (e.g. /build/gekkota/lib/de-DE), period!
Any idea?
I'm working on Fedora Core 1 with mono 0.29.99.20031226.
Thanks,
Gius_.
--
Giuseppe Greco
::agamura::
phone: +41 (0)91 604 67 65
mobile: +41 (0)76 390 60 32
email: [EMAIL PROTECTED]
web:www.agamura.com
---
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers
---
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers
--
Giuseppe Greco
::agamura::
phone: +41 (0)91 604 67 65
mobile: +41 (0)76 390 60 32
email: [EMAIL PROTECTED]
web:www.agamura.com
---
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers
Re: [nant-dev] ?
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 test=${project-structure.gif.uptodate}
exec
program=xcftoall
commandline=
--gif --output=${build.dir}/figures/image.gif figures/image.xcf/
/ifnot
Yes. We've decided that for single-file cases one should use function
instead, so you should write:
if test=${not file::up-to-date(build.dir +
'/figures/project-structure.xcf',
'figures/project-structure.gif')}
exec ... /
/if
Alternatively you may use uptodate with filesets:
uptodate
targetfiles
includes name=figures/project-structure.gif /
/targetfiles
sourcefiles
includes name=${build.dir}/figures/project-structure.xcf /
/sourcefiles
/uptodate
BTW. Gert, what do you think about allowing sub-expression evaluation in
strings so that we could write:
if test=${not
file::up-to-date('${build.dir}/figures/project-structure.xcf',
'figures/project-structure.gif')}
/if
Jarek
---
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers
Re: [nant-dev] ?
Nested 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:
if test=${not
file::up-to-date('${build.dir}/figures/project-structure.xcf',
'figures/project-structure.gif')}
/if
Jarek
---
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers
Re: [nant-dev] ?
I'll add this. One question: using nested expressions, we can have things
like this: (note the double quotes)
echo message=string::length('aaa ${string:length('''')} ccc')} /
or even (quadruple quotes):
echo message=string::length('${string::length(''aaa
${string:length()} ccc'')}')} /
Do we want to allow this?
I'd say - let's support nesting up to one level deep. What to you think?
Jarek
- Original Message -
From: Scott Hernandez [EMAIL PROTECTED]
To: NAnt Developers [EMAIL PROTECTED]
Sent: Saturday, January 10, 2004 8:10 PM
Subject: Re: [nant-dev] ?
Nested 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:
if test=${not
file::up-to-date('${build.dir}/figures/project-structure.xcf',
'figures/project-structure.gif')}
/if
Jarek
---
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers
---
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers
