Warn if deprecated properties are defined, but do not use it anymore
Description
As more an more properties have their default values configured and documented in shipped mycore.properties files. We cannot use the old behaviour to check for deprecated properties if a property is not set. This will not work reliable. Instead we should check all properties on start and throw an Exception for every deprecated property in use.
Environment
None
Activity
Sebastian Hofmann
January 4, 2017 at 9:45 AM
(edited)
Example case: I insert MCR.Module-iview2.DeveloperMode=MCR.Viewer.DeveloperMode to deprecated properties. In the properties of MyCoRe viewer module i set MCR.Viewer.DeveloperMode=false. In my old test Application i have MCR.Module-iview2.DeveloperMode=true so i can debug quickly.
I would now expect that MCR.Module-iview2.DeveloperMode in my application overwrites MCR.Module-iview2.DeveloperMode in the MyCoRe viewer module.
But the replace, link, whatever mechanic only works when the new property is not set in MyCoRe or in the Application.
Since we put all default properties in the mycore.properties file instead in the java code, this function makes no sense anymore.
As more an more properties have their default values configured and documented in shipped
mycore.properties
files. We cannot use the old behaviour to check for deprecated properties if a property is not set. This will not work reliable. Instead we should check all properties on start and throw anException
for every deprecated property in use.