[ http://issues.apache.org/jira/browse/FOR-739?page=comments#action_12359943 ]
Ross Gardler commented on FOR-739: ---------------------------------- Plugins can now provide default settings in PLUGIN_HOME/default.plugin.properties.xml The values in these files can be overridden by a project in PROJECT_HOME/forrest.properties.xml However, the implementation is not yet complete and will break when we use plugins in-place or move their location from build/plugins because this location is hard wired into ForrestConfUtils (see Subversion commits on this issue). Furthermore, in order for this to work there must be a *duplicate* setting of requried.forrest.plugins in the projects forrest.properties.xml - that is a duplicate setting to that found in forrest.properties. This is because plugins are still loaded by consulting forrest.properties for the list of plugins but the default properties are loaded by examining the setting in forrest.properties.xml We therefore need to change the plugin loading mechanism so that it uses forrest.properties.xml > Plugins to provide default property values > ------------------------------------------ > > Key: FOR-739 > URL: http://issues.apache.org/jira/browse/FOR-739 > Project: Forrest > Type: Sub-task > Components: Plugins (general issues), Core operations > Versions: 0.8-dev > Reporter: Ross Gardler > > Plugins need to be able to provide default values for properties they > require. This can be achieved by having > org.apache.forrest.conf,ForrestConfModule load the relevant properties files > after the project specific ones have been loaded and before the forrest > defauits are loaded. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
