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
