forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeff Turner <je...@apache.org>
Subject Re: Standard DTD (was Re: [VOTE] FakeForrest is ready!)
Date Tue, 07 Jan 2003 10:29:57 GMT
On Mon, Jan 06, 2003 at 03:33:03PM +1100, David Crossley wrote:
...
> > Forrest needs a bit of restructuring to support multiple
> > document types.
> > Each new doctype requires (at least):
> > 
> >  - schemas, currently in src/resources/schema/dtd
> >  - XSLTs, in src/resources/skins/common/xslt
> >  - catalog in src/resources/schema
> >  - sitemap mods
> > 
> > I was thinking we could package these up into RPM-like bundles,
> > so users could download new doctype support as they need it.
> > 
> > Forrest plugins. Hmm. Volunteers? :)
> 
> This would be truly excellent to have the infrastructure
> for such plugins. In this way, business could add value
> to Forrest and sell support packages for specialised
> communities. Anyway, back to building the infrastructure.
> 
> Great idea Jeff, i will help.
> 
> How would it work? Would the forrest-dev community
> maintain configuration files for each supported package
> which define where Ant will get the separate pieces and
> where to insert them into the local build?
>
> Or would Forrest have separate cvs modules to hold copies
> of the various released schemas, i.e. pre-prepared packages
> of all the bits, that would be maintained by forrest-dev?

So it's a choice of when the pieces are assembled: once by a Forrest dev,
or dynamically on the user's computer.

I've implemented the first with a handful of Ant scripts (which in turn
download others..) and ViewCVS:

http://marc.theaimsgroup.com/?l=forrest-dev&m=103770809113417&w=2

The second 'pre-packaged' thing is more ambitious, but still fairly
do-able.  Just a (signed) jar with a META-INF/control.xml Ant script
describing how to 'deploy' the jar contents to the Forrest installation.


--Jeff


> --David
> 

Mime
View raw message