Global/local property resolution

Today, I was trying a pattern something like this:

<cruisecontrol>
  <property name="build.root" value="/path/to/source/tree"/>
  <property name="build.dir" value="${build.root}/${project.name}"/>

...

  <project name="foo">
     <property file="${build.dir}/cc.properties"/>
....

If it makes a difference, the "foo" project definition is in a separate file
included with include.projects.

When I did this, I got a file not found error in my build loop for
"/path/to/source/tree/${project.name}/cc.properties".

It looks as though it isn't fully resolving the properties in this case.

I also tried adding a global property like this:

<property name="build.properties" value="${build.dir}/cc.properties"/>

and then changing the project-specific property line to:

<property file="${build.properties}"/>

That failed the same way.

If, however, I change the project-specific line to this:

<property file="${build.root}/${project.name}/cc.properties"/>

it works fine.

Is this a bug, or am I doing something wrong?

Thanks,
Randy
-- 
Randy Coulman
[email protected]

------------------------------------------------------------------------------
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

_______________________________________________
Cruisecontrol-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/cruisecontrol-user