From general-return-1798-apmail-logging-general-archive=logging.apache.org@logging.apache.org Sun May 20 22:07:51 2012 Return-Path: X-Original-To: apmail-logging-general-archive@www.apache.org Delivered-To: apmail-logging-general-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 8BE09C0BA for ; Sun, 20 May 2012 22:07:51 +0000 (UTC) Received: (qmail 17179 invoked by uid 500); 20 May 2012 22:07:50 -0000 Delivered-To: apmail-logging-general-archive@logging.apache.org Received: (qmail 17047 invoked by uid 500); 20 May 2012 22:07:50 -0000 Mailing-List: contact general-help@logging.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: "Logging General" List-Id: Delivered-To: mailing list general@logging.apache.org Received: (qmail 17039 invoked by uid 99); 20 May 2012 22:07:50 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 20 May 2012 22:07:50 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [212.27.42.3] (HELO smtp3-g21.free.fr) (212.27.42.3) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 20 May 2012 22:07:42 +0000 Received: from bigmax.localnet (unknown [82.231.48.193]) by smtp3-g21.free.fr (Postfix) with ESMTP id 1C6BAA621F for ; Mon, 21 May 2012 00:07:12 +0200 (CEST) From: =?ISO-8859-1?Q?Herv=E9?= BOUTEMY To: Logging General Subject: Re: Logging web sites Date: Mon, 21 May 2012 00:07:12 +0200 Message-ID: <5843285.pUSQA64zoO@bigmax> User-Agent: KMail/4.8.2 (Linux/3.2.0-24-generic; KDE/4.8.2; x86_64; ; ) In-Reply-To: References: <7F1F7665-D82D-4374-988C-F400A3610205@dslextreme.com> <2292772.PvrqEaSf2C@bigmax> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="nextPart3070227.jVrq9kkzZV" Content-Transfer-Encoding: 7Bit X-Virus-Checked: Checked by ClamAV on apache.org --nextPart3070227.jVrq9kkzZV Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1" The only modifications from classical "mvn site" build are: 1. the source directory: ${basedir}/content 2. the output directory: ${site.output}, to=20 be set from command line as -Dsite.output=3D... whatever infra wants Then extpath.txt is in content/resources, which will be available from=20= generated html (copied during "mvn site"):=20 https://svn.apache.org/repos/asf/maven/site/branches/INFRA-4466/trunk/c= ontent/resources/extpaths.txt The above concerns me a bit. Log4j2 is a multi-module site. My plan h= as=20 always been to use site:deploy or site:stage-deploy to get the site to=20= wherever it has to go to be processed by svnpubsub. From what you are s= aying I=20 can't tell if that will work or not as I would not modify the output di= rectory=20 for a multi-module build as it won't accomplish anything and I'm not su= re at=20 all why I would want to modify the siteDirectory to build the Log4j2 si= te. Ralph No problem with Log4j2, it wil work with "mvn site-stage" followed by "= mvn=20 scm-publish:publish-scm" without modifying siteDirectory nor outputDire= ctory. The modification to source and output directories are necessary for the= CMS to=20 take care of the build (detect changes, then publish the built result t= o svn). But sub-sites will be built by developers (while releasing), not by the= CMS:=20 there is no source nor output directories constraints. Herv=E9 --nextPart3070227.jVrq9kkzZV Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset="iso-8859-1"

https:= //svn.apache.org/repos/asf/maven/site/branches/INFRA-4466/trunk/content= /resources/extpaths.txt

<= br />

T= he above concerns me a bit. =A0Log4j2 is a multi-module site. =A0My pla= n has always been to use site:deploy or site:stage-deploy to get the si= te to wherever it has to go to be processed by svnpubsub. From what you= are saying I can't tell if that will work or not as I would not modify= the output directory for a multi-module build as it won't accomplish a= nything and I'm not sure at all why I would want to modify the siteDire= ctory to build the Log4j2 site.

<= br />

R= alph

<= br />

No = problem with Log4j2, it wil work with "mvn site-stage" follow= ed by "mvn scm-publish:publish-scm" without modifying siteDir= ectory nor outputDirectory.

 

The= modification to source and output directories are necessary for the CM= S to take care of the build (detect changes, then publish the built res= ult to svn).

 

But= sub-sites will be built by developers (while releasing), not by the CM= S: there is no source nor output directories constraints.

 

Her= v=E9

--nextPart3070227.jVrq9kkzZV--