[ http://issues.apache.org/jira/browse/FOR-799?page=comments#action_12364453 ]
Ross Gardler commented on FOR-799: ---------------------------------- wow, even more confusing, not core, or the theme.core plugin but forrest-core.xconf, one tiny word, so many meanings ;-) I get it now though, I may get some time to look at the dispatcher around the end of the week. If someone gets to this issue before me then an example of how to do this is in the Daisy plugin. Basically just add a default.plugin.properties.xml file with all the necessary values in it, for example: http://svn.apache.org/viewcvs.cgi/forrest/trunk/whiteboard/plugins/org.apache.forrest.plugin.input.Daisy/default.plugin.properties.xml?view=markup You'll need to remove the correcponding entries from forrest.properties as well. There is no need to change forrest.xconf or the sitemap as the new system is only on the input side, not the usage side, in other words there are no changes to the way we use properties. Individual projects can then override any of the values in their own forrest.properties.xml file (oe even locl.forest.properties.xml) For more info on the new properties system see FOR-588 > remove all references from the core to the dispatcher > ----------------------------------------------------- > > Key: FOR-799 > URL: http://issues.apache.org/jira/browse/FOR-799 > Project: Forrest > Type: Sub-task > Components: Core operations, Dispatcher (aka views) > Reporter: Thorsten Scherler > > They should be no direct references in the core for the dispatcher. > This should be done with the new plugin system forrest.properties.xml. -- 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
