[kepler-dev] [Bug 5129] adding and removing configuration properties could be made easier
bugzilla-daemon at ecoinformatics.org
bugzilla-daemon at ecoinformatics.org
Sun Jan 16 17:43:50 PST 2011
http://bugzilla.ecoinformatics.org/show_bug.cgi?id=5129
David Welker <david.v.welker at gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
--- Comment #4 from David Welker <david.v.welker at gmail.com> 2011-01-16 17:43:49 PST ---
I have added the ability to make what I call add directives. For example, in a
module, if you add a new folder called "configuration-directives" and a file
called "add.xml" in a module, you will have created a configuration directive
for the default "configuraion.xml" file for that module. If you would like to
make an add directive for a different file, say "myconfig.xml", you would
change the name of the add directive file by simply appending -add.xml to the
file name. So, add directive for "myconfig.xml" would go in a file called
"myconfig-add.xml."
The contents of add directives can either be simple or complex or a combination
of both. For example, a configuration directive may simply make simple
additions:
<config>
<property1>myValue</property1>
<property2>myValue2</property2>
</config>
In this example, this add directive specifies that the simply properties
property1 and property2 should be added to configuration.xml.
A complex example is as follows:
<config>
<complexProperty>
<name1>myValue</name1>
<name2>myValue2</name2>
<name3>myValue3</name3>
</complexProperty>
</config>
In this example, this add directive specifies that this complex property with
three parts should be added to configuration.xml.
At this stage, I have decided not to add remove or change directives, as
further discussion is necessary regarding whether such directives are
desirable, and if so, how they should work.
Closing this bug.
--
Configure bugmail: http://bugzilla.ecoinformatics.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
More information about the Kepler-dev
mailing list