Thorsten Scherler wrote:
El jue, 05-01-2006 a las 16:14 +0100, Cyriaque Dupoirieux escribió:
Tim Williams a écrit :
On 1/5/06, Ross Gardler <[EMAIL PROTECTED]> wrote:
[EMAIL PROTECTED] wrote:
Author: crossley
Date: Wed Jan 4 23:01:23 2006
New Revision: 366100
URL: http://svn.apache.org/viewcvs?rev=366100&view=rev
Log:
Use minimal forrest.properties files.
Modified:
forrest/trunk/main/fresh-site/forrest.properties
forrest/trunk/main/template-sites/basic/forrest.properties
forrest/trunk/main/template-sites/benchmark/forrest.properties
forrest/trunk/main/template-sites/business/forrest.properties
forrest/trunk/main/template-sites/v3/forrest.properties
...
The solution David has chosen you still can define your minimum
configuration even if you just override one property. Besides he added a
nice header that you can add any given property again by looking up the
fresh-site file (we everything is pretty much described).
You are mixing the two commits David made. One was to clear out
unnecessary stuff from plugins etc. I'm +1 for that. The other is the
one above, this is for the template sites. These are used by users as a
starting point and therefore extra documentation in there will reduce
the number of questions we get on the mailing lists.
Another way is to define a svn:ext. Meaning all template sites would
keep the blown away properties to play around but we as project have to
maintain only one (e.g. the one from fresh-site).
+1 (for the seed sites only - I'm happy with the minimal stuff in
plugins etc. that are not used by users in the same way)
Ross
