You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by "Ross Gardler (JIRA)" <ji...@apache.org> on 2005/07/26 21:36:21 UTC
[jira] Created: (FOR-588) Design new config system
Design new config system
------------------------
Key: FOR-588
URL: http://issues.apache.org/jira/browse/FOR-588
Project: Forrest
Type: Task
Reporter: Ross Gardler
Priority: Blocker
Fix For: 0.8-dev
We need a new config system for Forrest to enable the specification of multiple Forrest sites. within a single instance of Forrest and to accomodate 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
Re: [jira] Created: (FOR-588) Design new config system
Posted by Ross Gardler <rg...@apache.org>.
Anil Ramnanan wrote:
> Ross Gardler (JIRA) wrote:
>
>>
>> We need a new config system for Forrest to enable the specification of
>> multiple Forrest sites. within a single instance of Forrest and to
>> accomodate the changes brought about by forrest:views, themes and
>> plugins.
>>
>>
>>
>
> What does this new config system mean for the forrest.properties file ?
We don't know exactly what will happen, it's been mentioned a number of
times and was discussed at ApacheCon. We haven't designed the solution
yet. See the issue I linked to for what little info there is at this stage.
One thing you can be fairly sure of is that forrest.properties will
disappear. You will see the discussion when everyone is back from
ApacheCon, so you will have plenty of chance to contribute.
> I am supposed to be building an editor or forrest.properties but myabe
> Is hould be building a Forrest configuration editor instead ?
Good point. It will, most likely, be driven by an XML schema, so
hopefully it will be pretty easy to create an editor for it. However,
you needn't worry about it at this stage. Obviously you can't write an
editor for something still being designed. So spend the time allocated
for that on helping us get the design right.
Ross
Re: [jira] Created: (FOR-588) Design new config system
Posted by Anil Ramnanan <li...@peppersauce.org>.
Ross Gardler (JIRA) wrote:
>
>We need a new config system for Forrest to enable the specification of multiple Forrest sites. within a single instance of Forrest and to accomodate the changes brought about by forrest:views, themes and plugins.
>
>
>
What does this new config system mean for the forrest.properties file ?
I am supposed to be building an editor or forrest.properties but myabe
Is hould be building a Forrest configuration editor instead ?
Anil.
[jira] Commented: (FOR-588) Design new configuration system
Posted by "David Crossley (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FOR-588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12573147#action_12573147 ]
David Crossley commented on FOR-588:
------------------------------------
More discussion is at:
RT: Storage of Properties
http://marc.info/?t=120370236700002
> Design new configuration system
> -------------------------------
>
> Key: FOR-588
> URL: https://issues.apache.org/jira/browse/FOR-588
> Project: Forrest
> Issue Type: Task
> Components: Core operations
> Reporter: Ross Gardler
> Priority: Critical
> Fix For: 0.9-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.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (FOR-588) Design new config system
Posted by "Ross Gardler (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/FOR-588?page=comments#action_12318676 ]
Ross Gardler commented on FOR-588:
----------------------------------
An RT on how to integrate multiple sites:
http://marc.theaimsgroup.com/?l=forrest-dev&m=112387459426160&w=2
> Design new config 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 to enable the specification of multiple Forrest sites. within a single instance of Forrest and to accomodate 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
[jira] Updated: (FOR-588) Design new configuration system
Posted by "Tim Williams (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FOR-588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tim Williams updated FOR-588:
-----------------------------
Fix Version/s: (was: 0.9-dev)
0.10
> Design new configuration system
> -------------------------------
>
> Key: FOR-588
> URL: https://issues.apache.org/jira/browse/FOR-588
> Project: Forrest
> Issue Type: Task
> Components: Core operations
> Reporter: Ross Gardler
> Priority: Critical
> Fix For: 0.10
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (FOR-588) Design new configuration system
Posted by "Ross Gardler (JIRA)" <ji...@apache.org>.
[ 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
[jira] Commented: (FOR-588) Design new configuration system
Posted by "Ross Gardler (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/FOR-588?page=comments#action_12331094 ]
Ross Gardler commented on FOR-588:
----------------------------------
Using locationmap as a config system: http://marc.theaimsgroup.com/?l=forrest-dev&m=112827771411900&w=2
> 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
[jira] Updated: (FOR-588) Design new config system
Posted by "Ross Gardler (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/FOR-588?page=all ]
Ross Gardler updated FOR-588:
-----------------------------
Component: Core operations
> Design new config 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 to enable the specification of multiple Forrest sites. within a single instance of Forrest and to accomodate 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
[jira] Updated: (FOR-588) Design new config system
Posted by "David Crossley (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/FOR-588?page=all ]
David Crossley updated FOR-588:
-------------------------------
Comment: was deleted
> Design new config 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 to enable the specification of multiple Forrest sites. within a single instance of Forrest and to accomodate 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
[jira] Commented: (FOR-588) Design new config system
Posted by "Ross Gardler (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/FOR-588?page=comments#action_12316792 ]
Ross Gardler commented on FOR-588:
----------------------------------
Nikola drew some notes from a Hackathon meeting between various Forrest devs: http://svn.apache.org/viewcvs.cgi/forrest/trunk/etc/Stuttgart%202005%20Hackatron/
> Design new config system
> ------------------------
>
> Key: FOR-588
> URL: http://issues.apache.org/jira/browse/FOR-588
> Project: Forrest
> Type: Task
> Reporter: Ross Gardler
> Priority: Blocker
> Fix For: 0.8-dev
>
> We need a new config system for Forrest to enable the specification of multiple Forrest sites. within a single instance of Forrest and to accomodate 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
[jira] Updated: (FOR-588) Design new configuration system
Posted by "Ross Gardler (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/FOR-588?page=all ]
Ross Gardler updated FOR-588:
-----------------------------
Fix Version: 0.9
(was: 0.8-dev)
Priority: Critical (was: Blocker)
We have a prototype solution in place for 0.8-dev
This solution solves the immediate problems for configuring plugins.
Reducing priority and moving to 0.9 when we will complete this functionaliy.
> 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: Critical
> Fix For: 0.9
>
> 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
[jira] Commented: (FOR-588) Design new config system
Posted by "David Crossley (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/FOR-588?page=comments#action_12318860 ]
David Crossley commented on FOR-588:
------------------------------------
This issue is the result of an ApacheCon discussion, more, including links to the original ApacheCon Summaries at :- FOR-618 "Create issues for items discussed at Apachecon"
Some devs had an initial discussion. The notes are in SVN at
http://svn.apache.org/repos/asf/forrest/events/apachecon-eu-2005/
> Design new config 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 to enable the specification of multiple Forrest sites. within a single instance of Forrest and to accomodate 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
[jira] Updated: (FOR-588) Design new configuration system
Posted by "David Crossley (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/FOR-588?page=all ]
David Crossley updated FOR-588:
-------------------------------
Summary: Design new configuration system (was: Design new config system)
Description: 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. (was: We need a new config system for Forrest to enable the specification of multiple Forrest sites. within a single instance of Forrest and to accomodate the changes brought about by forrest:views, themes and plugins.)
> 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
[jira] Commented: (FOR-588) Design new config system
Posted by "Ross Gardler (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/FOR-588?page=comments#action_12318313 ]
Ross Gardler commented on FOR-588:
----------------------------------
Some discussion:
http://marc.theaimsgroup.com/?t=112299875300003&r=1&w=2
> Design new config system
> ------------------------
>
> Key: FOR-588
> URL: http://issues.apache.org/jira/browse/FOR-588
> Project: Forrest
> Type: Task
> Reporter: Ross Gardler
> Priority: Blocker
> Fix For: 0.8-dev
>
> We need a new config system for Forrest to enable the specification of multiple Forrest sites. within a single instance of Forrest and to accomodate 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
[jira] Commented: (FOR-588) Design new config system
Posted by "David Crossley (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/FOR-588?page=comments#action_12318861 ]
David Crossley commented on FOR-588:
------------------------------------
NOTE: For any users thinking ("oh no, the next forrest will be hard to upgrade because of fundamental changes in the way it is configured", don't worry. We will (most likely) provide tools to facilitate this upgrade, we will need them ourselves anyway).
> Design new config 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 to enable the specification of multiple Forrest sites. within a single instance of Forrest and to accomodate 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