Ross Gardler wrote: > David Crossley wrote: > >David Crossley wrote: > >>As mentioned there, Reinhard did some experimentation > >>at Cocoon-2.2 (pre Daisy docs) that used svn:externals > >>to maintain the forrest.properties and skinconf.xml etc. > >>I will investigate and report back. I get the feeling > >>that it only operates at directory level. > > > >Here is a summary of his technique. There are two aspects: > >- including copy of common configuration files via svn:externals > >- using xml entities to manage common sections of xml files > > > >Standard configuration files are at > >http://svn.apache.org/repos/asf/cocoon/site/src/forrest-configuration > >There are various things here such as sitemap.xmap > >and stylesheets which we would not need for our situation. > > > >Using 'svn:externals' this directory is created wherever it > >is needed, e.g. under > >http://svn.apache.org/repos/asf/cocoon/trunk/src/documentation/src > >So the tree is ... > > documentation > > |-- forrest.properties > > |-- src (this second src directory was a forrest config mistake) > > |-- content > > |-- forrest-configuration <--------- > > |-- skinconf.xml > > > >The forrest.properties refers to resources in the > >forrest-configuration directory. > > > >The skinconf.xml declares some of its own stuff, > >and includes other skinconf.xml files by using > >xml entities. Clever. > > > > --oOo-- > > > >So we could use this technique for managing the config > >files of our plugins. At the moment the only ones > >that i can think of is skinconf.xml and maybe the > >CatalogManager.properties file. Later we might need > >to include others. > > > >What do you reckon? > > Sounds like a great idea.
I changed my mind. For the common skinconf stuff, use a centralised xml entity. It is neat. (svn r367219) There is too much overhead with the abovementioned svn:externals technique to use it just for this common skinconf stuff. Pehaps later for other common config. -David
