Adrian Dębowski wrote:
> Hi,
>
> I was Ant user and recently switched do NAnt. I wish to ask if some
> little diffcence between them I have observed, is a feature, bug or
> simple my mistake.
>
> I used to write some global parameters (<path>) in root build file:
>
> <?xml version="1.0" encoding="UTF-8" ?>
> <project name="frs.src" default="build">
> <property name="frs.root" location=".." />
> <property name="frs.source" location="${frs.root}/src" />
>
> <path id="common.include.path">
> <pathelement path="${frs.source}/cmn/template" />
> </path>
>
>
> and then use them in many other subprojects:
>
>
> <?xml version="1.0" encoding="UTF-8" ?>
> <project name="FrsAstronomy" default="error">
> <target name="build">
> <dcc srcfile="frs/Tools/Tools.dpr" debug="false">
> <includepath refid="common.include.path" />
> </dcc>
> </target>
> </project>
>
> This works fine in Ant, but doesn't work at all in NAnt.
> "common.include.path" is not defined.
> It seems that <path> elements are local only. Is it true?
>
>
I don't see documentation for the <dcc> task on either the NAnt or
NAntContrib sites, so I'm not sure what it's expecting for includepath.
My guess is that it's looking for a string or property and not a <path>,
and hence can't find it. In any event, you might be able to do this
either using ordinary properties or using the <setenv> task (which does
take <path> elements).
Gary
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NAnt-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/nant-users
