fyi
-------- Original Message --------
Subject: Re: Implement svnpubsub using "mvn site" ?
Date: Thu, 16 Feb 2012 09:48:59 -0800 (PST)
From: Joe Schaefer <[email protected]>
Reply-To: Joe Schaefer <[email protected]>
To: Joe Schaefer <[email protected]>, Eric Charles
<[email protected]>, Apache Infrastructure
<[email protected]>
----- Original Message -----
From: Joe Schaefer <[email protected]>
To: Eric Charles <[email protected]>; Apache Infrastructure
<[email protected]>
Cc:
Sent: Thursday, February 16, 2012 12:22 PM
Subject: Re: Implement svnpubsub using "mvn site" ?
________________________________
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.
FWIW Benson, having maven build the javadocs to an svn-1.7 working copy
in a way
that manages adds and deletes properly is where I really see a need for
an asf
maven plugin. If you do it well you can tell maven the svn url of where to
get/put those built objects instead of dealing with svn externals, and
it will
be perfectly compatible with git-based projects with a little .gitignore
magic.
Actually doing site builds is something I'd really suggest people take a
good
look at the CMS for. The basic principle is to take most of the pain of
site
management out of the committer's coding workflow and onto the web where
it belongs.
No reason why in this day and age a committer needs to be running mvn
site and
mvn site-deploy on their own machines unless they really really need to.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
