fyi
-------- Original Message --------
Subject: Re: Implement svnpubsub using "mvn site" ?
Date: Thu, 16 Feb 2012 09:22:27 -0800 (PST)
From: Joe Schaefer <[email protected]>
Reply-To: Joe Schaefer <[email protected]>
To: Eric Charles <[email protected]>, Apache Infrastructure
<[email protected]>
________________________________
From: Eric Charles <[email protected]>
To: Apache Infrastructure <[email protected]>
Sent: Thursday, February 16, 2012 3:34 AM
Subject: Re: Implement svnpubsub using "mvn site" ?
Hi Joe,
All subprojects (and the main project) sites are built with mvn site (xml to
html).
- We have a 'site' project where we put the generated html, and the we made
'svn up' on people.apache.org.
- For whatever reason, we came to scp only the changed files/sites, so our
'site' project in svn in no more up-to-date...
- Optionally, we use mvn site-deploy directly (it has worked a few times, but
now seems broken due to bade credential).
Eww, let's see if we can throw most of that mess away and consolidate
the James
site builds into a single CMS-backed website. First we need to create a
james/site/trunk/content
directory in svn that contains all the xml files that serve as sources
for the entire site,
including the generated javadocs. Individual subprojects can checkout
and make changes to
whatever subtree of that directory they are interested in, and they can
use svn externals
to map the "javadoc" output subdirs back into their pristine source code
trees. Subprojects
then would only be responsible for building their local documentation
and checking it back in
to the svn:external based subdir that originates in the
james/site/trunk/content tree.
The rest is all handled cleanly by the CMS once someone figures out how
to instruct maven
to build a local checkout of james/site/trunk/content to a target
directory specified at runtime.
Whatever auxiliary config files, executables and libraries can all be
placed alongside
the james/site/trunk/content dir somewhere. The CMS will always start
the site build
using james/site/trunk as the current working directory. Those prebuilt
javadocs in
the content/ dir should simply be treated like any javascript, css, or
image file and
copied over unmodified.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
