forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeff Turner <je...@apache.org>
Subject Re: skinconf.xml , single configuration point?
Date Wed, 20 Nov 2002 14:17:47 GMT
On Wed, Nov 20, 2002 at 02:37:24PM +0100, Nicola Ken Barozzi wrote:
> 
> To reduce the number of files needed for forrest, I would propose to 
> move all forrest.properties under skinconf.xml, and that file be used in 
> Ant via XmlProperty.

They don't configure the skin, should why should they be in skinconf?

> This way we have only one configuration file.

Then how about:
 - merging forrest.properties into properties.xml
 - merging skinconf.xml into module.xml

Merging skinconf.xml and module.xml was always the plan, since they both
contain generic project metadata.

I don't reeeally see much benefit in merging skinconf and module though..

Advantage: we don't duplicate the <project-name/> in skinconf.xml with
<project name="..."/> in module.xml
Disadvantage: we force module.xml on projects that may not want it


--Jeff

> We still need though a place to say where we have *that* file though, so 
> the options are:
>  1) move skinconf.xml to top dir instead of forrest.properties
>  2) keep the double possibility, so forrest.properties takes precedence 
> and can set the location of skinconf.xml
>  3) the user sets it via the Ant invocation
>  4) the file is searched for automatically and the location cached in 
> the user's home dir.
> 
> I'd say (2), so that users with the src/documentation layout can remove 
> forrest.properties alltogether.
> 
> Thoughts?
> 
> -- 
> Nicola Ken Barozzi                   nicolaken@apache.org
>             - verba volant, scripta manent -
>    (discussions get forgotten, just code remains)
> ---------------------------------------------------------------------
> 

Mime
View raw message