Hans Dockter wrote:
There are some areas where properties have pretty long names to
describe the context they belong to. On example is archivesBaseName
and archivesTaskBaseName. In such case it might be an better to
provide some additional context.
For example:
archives.baseName
archives.tasksBaseName
I think this a good idea, not just because of the name spacing it
provides. The 'archives' name space can point at an object, which I can
replace with my own implementation if, say, I don't like how the archive
names are generated. That is, I can provide my own behaviour, not just
my own configuration.
We should do the same for the version/module/group/status properties as
well.
Adam
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
