[kepler-dev] [Bug 5129] New: adding and removing configuration properties could be made easier

[bugzilla-daemon at ecoinformatics.org]

http://bugzilla.ecoinformatics.org/show_bug.cgi?id=5129

           Summary: adding and removing configuration properties could be
                    made easier
           Product: Kepler
           Version: 2.0.0
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: general
        AssignedTo: berkley at nceas.ucsb.edu
        ReportedBy: barseghian at nceas.ucsb.edu
         QAContact: kepler-dev at kepler-project.org
   Estimated Hours: 0.0


Now that we've shipped 2.0, if a developer wants to add a new configuration
property to a config file, they must first check if the user's config file has
the property before accessing it, and add it if not. This is a minor hassle if
your code tries to use this property in a number of places, each of which might
be reached first during the user's kepler session...you have to do the check
and possible add at each place. Instead, maybe the configuration manager could,
during startup, run through all active modules config files and add properties
if necessary to the user's copies in KeplerData. Handing removing properties
would be harder -- if we remove a property, and then a user reverts to an older
version of Kepler, this CM method would have to know to add the property back
for that version.

-- 
Configure bugmail: http://bugzilla.ecoinformatics.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.