> ------- Additional Comments From [EMAIL PROTECTED] 2007-08-02 14:08 ------- > (In reply to comment #5) >> (In reply to comment #4) >>> I see two solutions: >>> >>> - modules and publications have to use name prefixes >>> >>> - properties have to be saved (and may only be read) together with an >>> "owner id" >> i think we should make prefixes mandatory: for modules, it should be >> <module-name>.your.property. for publications, it could be >> <pub-id>.your.property, but i guess we should leave the choice to the admin. >> users may also want to overload global properties... >> > > I am as well for prefixing, additional a check/record of double named > properties. > >> plus we need to find out and document really well in which order properties >> are >> loaded and how to override them. > > The case of double properties is very common because we implement a fallback > mechanism aka ant properties files. > > Ant properties work the following order: > 1. cli (e.g. -Dmodule=a) > 2. build files - normally more then one (local.)build.properties. First in > wins. > > For us it is (before the patch) > a) SystemProperties > b) local.lenya.properties.xml > c) modules > d) lenya.properties.xml > > I thought I wrote some documentation about it but cannot find it.
I think it would be nice if the publication properties could go between a) and b) but afair as the patch is now they are on top of a). I think this could only be changed if the system properties can be distinguished from the rest (by a name prefix?) so that the publication can leave them alone and not override them. WDYT? Markus Angst --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
