Howdy, I would think we really don't ;) I like Henri's simplification ideas. I would add something that interested me last night:
I had to update both the main (jakarta.apache.org) and commons (jakarta.apache.org/commons) sites. I committed my changes into CVS, no problem. Simply running ant (no args) on jakarta-site2 works, and it uses anakia/velocity as well. The same thing didn't work for commons, as it couldn't find the Anakia taskdef. Would simply copying the relevant part's from jakarta-site2's build.xml work for us? We wouldn't even have to re-invent the wheel ;) Yoav Shapira On Wed, 13 Aug 2003 [EMAIL PROTECTED] wrote: > Do we really need a webapp and database for static content? > -- > dIon Gillard, Multitask Consulting > Blog: http://blogs.codehaus.org/people/dion/ > > > news <[EMAIL PROTECTED]> wrote on 13/08/2003 10:40:49 AM: > > > One way to maintain Jakarta web sites, such as commons, of course is to > > use a CMS system. > > Store XML in a database (such as PostgreSQL), and edit remotely, flag as > > > approved, have it pre-render to HTML, and have a jSTL emit it. Since > > content is in DB, it is easy to manager. Since it's a web app, it is > > easy to modify. Of course, ver fast. > > Here is one example of Open Source CMS w/ a working URL: > > http://basicportal.com/do/cmsPg?content=DEVELOPMENT > > > > See the url? > > This makes a call to db to retrieve this content where = "DEVELOPMENT". > > (Of course DB is cached auto by DAO so no ping if no change) > > Realy, change the web site is easy, it's a lot like Wiki, except it has > > J2EE JDBC realms as to who can author and who can approve. > > > > .V > > > > > > Craig R. McClanahan wrote: > > > > > On Mon, 11 Aug 2003, Glenn Nielsen wrote: > > > > > > > > >>Date: Mon, 11 Aug 2003 21:56:46 -0500 > > >>From: Glenn Nielsen <[EMAIL PROTECTED]> > > >>Reply-To: Jakarta Commons Developers List > <[EMAIL PROTECTED]> > > >>To: Jakarta Commons Developers List <[EMAIL PROTECTED]> > > >>Subject: Re: [docs] Crappy build system > > >> > > >>Henri Yandell wrote: > > >> > > >>>Jakarta Commons build system for the website is very very crappy. > > >>>Regardless of whether things move to Maven or some other look and > feel, > > >>>I'd like to check in the jars needed so that people don't have to go > > >>>around hunting in jakarta-velocity, jakarta-site2 and who knows where > > >>>else. > > >>> > > >>>Is anyone against this? Is there some reason for the current > confusing > > >>>setup? > > >>> > > >> > > >>-1 to checking the jars into CVS > > > > > > > > > Agreed. Changing the site generaton process to use Maven would > eliminate > > > any need for this. > > > > > > Of course, so would using standard XML technologies like XSLT, but I'm > not > > > going to volunteer to maintain the Commons site sources, so I'm not > going > > > to go there :-). > > > > > > Craig > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
