Property resolution.

Hi,

 

I am struggling with inconsistent behaviour in my CC config files.

 

For example I have an artifactspublisher in a project and I am getting
error messages saying the target doesn't exist. It does exist, but the
clue seems to be that the message shows a path that contains unresolved
property references. It looks to me as if the file attribute of the
artifactspublisher is not resolved for properties within the scope where
it lies (i.e. the project).

 

I expected that all strings in the config file where I can use property
references would be fully resolved if possible at the point of use but
it seems that isn't what happens. I have a property that itself resolves
to a property reference which is defined in an inner scope, most of the
time this works so long as the property reference in the value has a
value itself at the point of use. I assumed this was the way properties
were supposed to work given the fact that CC provides the
${project.name} property that uses deferred resolution.

 

I can only assume that strings that are allowed to contain property
references are not resolved at the point of use in some (maybe all)
plugins which seems a missed opportunity to me.

 

Can someone explain why defined properties are left unresolved when it
would seem trivial to call the resolver recursively until no more
property references can be resolved just before the string is used?

 

Regards

Bill Somerville.

------------------------------------------------------------------------------
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2

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