I can help with logistical stuff on the people.apache.org end.
Typically, pages are composed using whatever the project desires, and
built pages get checked into subversion. An 'svn checkout' on
people.apache.org 'publishes' the web site (and 'svn up' publishes any
updates).
At first it struck me as kind of weird that anyone would check built
pages into subversion. The rationale is if the machine hosting the web
server dies, a replacement can be brought it, then infra can republish
project web sites with series of 'svn co'.
That much said, not all projects check in built pages. One example is
the db project site, which gets published via a "maven site:deploy".
-jean
Andrus Adamchik wrote:
> Since we now can migrate the web site to Apache, maybe we should
> investigate what it takes to build a maven site. The requirements to
> the site would be:
>
> * Preserve the current Cayenne skin
> * Include doc sections for different releases.
>
> Any volunteers to look into that?
>
> FYI, the current web site sources are separate from the main source
> tree in CVS:
>
> http://cvs.sourceforge.net/viewcvs.py/cayenne/cayenne-site/
>
> Andrus
>
>
> On Apr 28, 2006, at 2:54 PM, Kevin Menard wrote:
>
>> You guys probably already saw this, but if not, I'm including the TSS
>> link:
>>
>> http://www.theserverside.com/news/thread.tss?thread_id=40126
>>
>> I've only read through the first chapter, so I can't comment much on
>> its utility yet. I can say that it looks like the book was not
>> edited all that well and that they make some rather large,
>> unsubstantiated claims. If you can get past these things though, it
>> looks to be a fairly easy read that may be useful to those of us just
>> getting introduced to Maven.
>>
>> --
>> Kevin
>
>
This archive was generated by hypermail 2.0.0 : Mon May 01 2006 - 19:33:12 EDT