I'm not sure this is 100% germane, but the guys over at Turbine have been doing a lot of work in creating a unified project management system (probably that's not the best name for it). It's called Maven, and you can head to http://jakarta.apache.org/turbine/maven to find more information. With it, you can generate everything (build system, docs, metrics, web site, more) from one centralized project descriptor. The project is today at the point where all the Turbine subprojects have been moved to use Maven; perhaps it would be a good idea to consider it.
FYI, the guy behind Maven is Jason van Zyl. -- Gonzalo A. Diethelm [EMAIL PROTECTED] > -----Original Message----- > From: Jeff Turner [mailto:[EMAIL PROTECTED]] > Sent: Friday, March 22, 2002 01:02 AM > To: Avalon Developers List > Subject: Re: Cocoon 4 docs == complex > > > On Fri, Mar 22, 2002 at 03:14:27PM +1100, Peter Donald wrote: > > On Fri, 22 Mar 2002 09:24, Jeff Turner wrote: > > > It would be kinda nice to "outsource" the build system > development. Make > > > build system improvements part of another project, not Avalon. Better > > > SoC :) > > > > We can push it into jakarta-site when it is done I guess ;) > > Something I only just noticed today: Cocoon and Avalon use a > different DTD to > the rest of Jakarta (eg jakarta-site2). The 'stylebook' format is: > > <document> > <header> > ... > </header> > <s1 title="..."> > ... > <s2 title="..."> > ... > </s2> > </s1> > </document> > > and the jakarta-site2 format is: > > <document> > <properties> > ... > </properties> > <section name="..."> > </section> > ... > </document> > > > So we couldn't use jakarta-site2 out the box. Anyone know the > history of that > change? Or could this be the difference between jakarta-site and > jakarta-site2? > > > > A possible course of action: > > > > > > 1. We take this Centipede project template, and add a module for > > > building docs with Anakia or <style>. > > > > Not sure what you mean - isn't centipede cocon only? > > Centipede's build.xml uses entities: > > <!DOCTYPE project [ > ... > <!ENTITY docs-target SYSTEM "./tools/centipede/targets/docs.xtarget"> > ]> > > <project> > ... > &docs.target; > ... > </project> > > > So to replace the Cocoon doc system (docs.xtarget) with an Anakia or > <style> based one would be easy. > > ... > > I would prefer something extremely simple for users. I was > going to just do > > an XSL transformation via <style/>. All the products already > require xalan > > for generating the junit/jdepend/checkstyle reports so we could > reuse that > > and not require any more downloads. > > +1 > > I'll have a play tonight.. > > --Jeff > > > Thoughts? > > > > -- > > Cheers, > > > > Pete > > > > -------------------------------- > > My opinions may have changed, > > but not the fact that I am right > > -------------------------------- > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
