[
http://issues.apache.org/jira/browse/FOR-588?page=comments#action_12358112 ]
Ross Gardler commented on FOR-588:
----------------------------------
A new set of properties can now be defined in a "forrest.properties.xml" file
in the root of the project. These properties are not defined in forrest.xconf,
thus any property can be defined in this file. This enables plugins to define
their own property values. Although at the time of writing functionality is
minimal.
The format of the file is:
<?xml version="1.0" encoding="UTF-8"?>
<properties>
<property name="daisy.navigation.docID" value="1208"/>
</properties>
Properties are retrieved in the sitemap and the locationmap (untested) using
{project:PROPERTY.NAME}.
Currently there is no mechanism for loading defaults for plugin properties.
This needs to be added.
In addition to plugins being able to define properties that can be overridden
by the project properties file this addition enables us to remove the need to
define properties in forrest.xconf.
> Design new configuration system
> -------------------------------
>
> Key: FOR-588
> URL: http://issues.apache.org/jira/browse/FOR-588
> Project: Forrest
> Type: Task
> Components: Core operations
> Reporter: Ross Gardler
> Priority: Blocker
> Fix For: 0.8-dev
>
> We need a new config system for Forrest for various reasons: the initial
> config system was known to be limited; to enable the specification of
> multiple Forrest sites within a single instance of Forrest; to accommodate
> the changes brought about by forrest:views, themes, and plugins.
--
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
