You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by David Crossley <cr...@apache.org> on 2007/03/28 07:44:07 UTC

document the new properties system

Should we document the start of the new properties system?
I know that it is still prototype, but we need to encourage
developers to use it.

There some already some vague mentions of it
in our changes.html

Some plugins are already using it:

]$ find plugins -name "*properties*.xml"

plugins/org.apache.forrest.plugin.input.projectInfo/default.plugin.properties.xml
plugins/org.apache.forrest.plugin.input.projectInfo/forrest.properties.xml
plugins/org.apache.forrest.plugin.output.Text/default.plugin.properties.xml

As well as whiteboard plugins:
Daisy, dispatcher, NoteTaking, solr

And Dispatcher uses it in:
main/fresh-site/forrest.properties.xml
main/template-sites/basic/forrest.properties.xml

------------------------------
https://issues.apache.org/jira/browse/FOR-734
"Document new forrest.properties.xml file"

https://issues.apache.org/jira/browse/FOR-588
"Design new configuration system"

Re: document the new properties system

Posted by Ross Gardler <rg...@apache.org>.
Ross Gardler wrote:
> David Crossley wrote:
>> Should we document the start of the new properties system?
>> I know that it is still prototype, but we need to encourage
>> developers to use it.
> 
> Yes, but not at the expense of actual code things for the release 
> (unless someone has the desire to document it of course). We can update 
> documentation after release.

I should have pointed out that the system is reasonably well documented 
in the issue tracker and archives - so if someone does tackle this you 
should start there.

Ross

Re: document the new properties system

Posted by Ross Gardler <rg...@apache.org>.
David Crossley wrote:
> Should we document the start of the new properties system?
> I know that it is still prototype, but we need to encourage
> developers to use it.

Yes, but not at the expense of actual code things for the release 
(unless someone has the desire to document it of course). We can update 
documentation after release.

Which reminds me, we need to discuss what is going in the release package.

Ross