For large multi-module Ivy projects, it's nice to be able to specify ivy branches/revisions of shared dependencies in a common property file instead of hardcoding them across all the ivy.xml files. Currently, this means that Hudson will no longer be able to properly wire together the different Hudson Ivy Projects since it can't resolve these properties when parsing the ivy.xml files.

Allowing the user to specify a comma-delimited list of property files in the job config to be loaded before parsing would resolve this.