On 26/10/2007, Jacob Grydholt Jensen <[EMAIL PROTECTED]> wrote: > > - a new override attribute on the settings task determines what > happens if an id is not unique. The override attribute can be one of > "true | false | notallowed" with notallowed being the default. The > meaning of this attribute should be: > - notallowed : an error is raised if a settings has already > been defined with this id > - true : the current settings will take precedence over any > previously defined setting with this id > - false : the current settings will not override a previously > defined setting with this id
Sorry for replying to my own mail, but I gave this some more thought. Is it possible for the subprojects to meaningfully override the mainproject's id in ant? If these id are shared (aliased) between the mainproject and the subproject the subproject could end up overwriting the mainproject's settings which would cause havoc when the flow of control returns to the main project's build. /grydholt
