The actual problem is that I have some top-level include file that contains
stuff like:
<property name="dir.root" value="${path::get-full-path('..\')}" />
<property name="dir.imports" value="${dir.root}Imports" />
<property name="dir.trunk" value="${dir.root}Trunk" />
.....
I want these properties set when I include them in my build files. There is
a variety of top-level directories that my build scripts will need to know
about. Basically these properties need to be set based on the current
directory of the include file, not the build file that includes this file.
--
View this message in context:
http://www.nabble.com/Getting-the-Path-of-an-Included-Build-File-tp25025552p25026889.html
Sent from the NAnt - Users mailing list archive at Nabble.com.
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
NAnt-users mailing list
NAnt-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-users
