From server-dev-return-49088-apmail-james-server-dev-archive=james.apache.org@james.apache.org Thu Feb 16 19:36:14 2012 Return-Path: X-Original-To: apmail-james-server-dev-archive@www.apache.org Delivered-To: apmail-james-server-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3A5A398B4 for ; Thu, 16 Feb 2012 19:36:14 +0000 (UTC) Received: (qmail 47133 invoked by uid 500); 16 Feb 2012 19:36:14 -0000 Delivered-To: apmail-james-server-dev-archive@james.apache.org Received: (qmail 47092 invoked by uid 500); 16 Feb 2012 19:36:14 -0000 Mailing-List: contact server-dev-help@james.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "James Developers List" Reply-To: "James Developers List" Delivered-To: mailing list server-dev@james.apache.org Received: (qmail 47084 invoked by uid 99); 16 Feb 2012 19:36:14 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 16 Feb 2012 19:36:14 +0000 X-ASF-Spam-Status: No, hits=3.6 required=5.0 tests=FSL_HELO_NON_FQDN_1,HELO_LOCALHOST,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [91.183.38.48] (HELO localhost) (91.183.38.48) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 16 Feb 2012 19:36:07 +0000 MIME-Version: 1.0 X-UserIsAuth: true Received: from 91.178.203.27 (EHLO ech.local) ([91.178.203.27]) by srv002 (JAMES SMTP Server ) with ESMTPA ID 1877930322; Thu, 16 Feb 2012 08:35:45 +0100 (CET) Message-ID: <4F3D5A90.4090007@u-mangate.com> Date: Thu, 16 Feb 2012 20:35:44 +0100 From: Eric Charles User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:10.0.1) Gecko/20120208 Thunderbird/10.0.1 To: James Developers List Subject: Fwd: Re: Implement svnpubsub using "mvn site" ? References: <1329412947.44060.YahooMailNeo@web160903.mail.bf1.yahoo.com> In-Reply-To: <1329412947.44060.YahooMailNeo@web160903.mail.bf1.yahoo.com> X-Forwarded-Message-Id: <1329412947.44060.YahooMailNeo@web160903.mail.bf1.yahoo.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit fyi -------- Original Message -------- Subject: Re: Implement svnpubsub using "mvn site" ? Date: Thu, 16 Feb 2012 09:22:27 -0800 (PST) From: Joe Schaefer Reply-To: Joe Schaefer To: Eric Charles , Apache Infrastructure >________________________________ > From: Eric Charles >To: Apache Infrastructure >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: server-dev-unsubscribe@james.apache.org For additional commands, e-mail: server-dev-help@james.apache.org