From general-return-1784-apmail-logging-general-archive=logging.apache.org@logging.apache.org Sat May 19 20:35:39 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 DC88D9D9D for ; Sat, 19 May 2012 20:35:39 +0000 (UTC) Received: (qmail 55136 invoked by uid 500); 19 May 2012 20:35:39 -0000 Delivered-To: apmail-logging-general-archive@logging.apache.org Received: (qmail 55080 invoked by uid 500); 19 May 2012 20:35:39 -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 55071 invoked by uid 99); 19 May 2012 20:35:39 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 19 May 2012 20:35:39 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of ralph.goers@dslextreme.com designates 209.85.210.47 as permitted sender) Received: from [209.85.210.47] (HELO mail-pz0-f47.google.com) (209.85.210.47) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 19 May 2012 20:35:33 +0000 Received: by dalh21 with SMTP id h21so5456007dal.34 for ; Sat, 19 May 2012 13:35:11 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=sender:subject:references:from:content-type:x-mailer:in-reply-to :message-id:date:to:content-transfer-encoding:mime-version :x-gm-message-state; bh=u3kng9zpa8D0zLYpG4Gukc2D1yNeVexkcMvpy7YTwN8=; b=H3uA5isXdcU9isaDyUSv/m7k0BbReakiNPoM/Pe2myPki6S6gkWmiaikJ181WR/ql/ zQa0hJHAOgY4dz/80UptO4X2IK4QQuDtM8Ces50ZOJlrL6zsvR666XrRdE8aoDiLN8iV 2i+eSKKymc3Qb7kd1y6gej7PWnMv4xHvXLQMt88pMRu4WI6gvAeIY1+8gobcPFqmDvZl Koa61U1YKlrrqBr/ApDTC0iRStT9ppG+fp4Wcq+sbjdndzeaTzdbcKFD+AhXEOOd+aV9 o0Ty6AN9vK2aQRQI7F3Qscp9DT5jiGQeAv5sM9eObqIIEkLKVaK51nqtPyYXMzo4UXbB 7o3Q== Received: by 10.68.238.73 with SMTP id vi9mr19810292pbc.14.1337459711466; Sat, 19 May 2012 13:35:11 -0700 (PDT) Received: from [192.168.1.80] (99-180-69-21.lightspeed.irvnca.sbcglobal.net. [99.180.69.21]) by mx.google.com with ESMTPS id nd6sm17270704pbc.63.2012.05.19.13.35.08 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 19 May 2012 13:35:09 -0700 (PDT) Sender: "ralph.goers @dslextreme.com" Subject: Re: Logging web sites References: <7F1F7665-D82D-4374-988C-F400A3610205@dslextreme.com> <5A721A48-89B0-41E1-A245-CB62837C1B36@dslextreme.com> <68FC237E-97CF-418E-8AAF-1ED6C7E21635@dslextreme.com> <5C8B3DE5-AA06-4548-96D9-27A0EE5B8D97@dslextreme.com> <2913190B-6E3B-4223-B3FF-98A09CCF89EB@dslextreme.com> <57031363-953A-4356-BF8E-2B33FD18E06E@apache.org> From: Ralph Goers Content-Type: text/plain; charset=us-ascii X-Mailer: iPad Mail (9B206) In-Reply-To: <57031363-953A-4356-BF8E-2B33FD18E06E@apache.org> Message-Id: <2FA9ECF0-76A3-454D-8C28-8F59B44DB279@apache.org> Date: Sat, 19 May 2012 13:35:06 -0700 To: Logging General Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (1.0) X-Gm-Message-State: ALoCoQlUT2AIZzWfp7rQedCNGdla5xMOEqAAO/7lcRnKLAcjmrRN1zBz4CB60Ft/HF3lCHV9aaNN Oops. I meant maven-site-scm-publish plugin Ralph On May 19, 2012, at 1:33 PM, Ralph Goers wrote: > My understanding is the asf-svnpubsub-plugin is the predecessor to the mav= en-site-scm-plugin that I mentioned. >=20 > Ralph >=20 > On May 19, 2012, at 9:12 AM, Christian Grobmeier wro= te: >=20 >> I just found this: >> http://maven.apache.org/sandbox/plugins/asf-svnpubsub-plugin/index.html >>=20 >> Did we consider that one? It looks nice and integrates well with >> maven. It seems to checkout a specific url from svn, compares it with >> the locally generated site and then commits a diff to the publishing >> tree. =46rom there its taken by svnpubsub. >>=20 >> =46rom what I understood so far, it should be easiest to use that >> plugin. We would need to check out every site with every change, but >> as the pubsub works on a separate tree, i think its no problem. >>=20 >> WDYT? >>=20 >> On Sat, May 19, 2012 at 5:30 PM, Christian Grobmeier >> wrote: >>> On Fri, May 18, 2012 at 5:54 PM, Ralph Goers wrote: >>>> This topic has died down a bit. My concern here is that I am pretty mu= ch >>>> read to do a release of Log4j 2 but I really don't know how to publish t= he >>>> web site. The process I use to build Log4j 2 is >>>=20 >>> Thanks for brining up the topic again. >>>=20 >>>> 1. Check it out from SVN. >>>> 2. Run "mvn -P release-notes generate-resources (then commit the genera= ted >>>> notes for a real release). >>>> 3. Run "mvn -P apache-release install (this step would be replaced by m= vn >>>> release:prepare release:package in a real release) >>>> 4. Run mvn site (would be on the tagged branch). >>>> 5. Run mvn site:stage-deploy or mvn site:deploy to deploy the site >>>> somewhere. >>>>=20 >>>> I'm imagining that I would need to use the maven-site-scm-publish plugi= n to >>>> commit the site to where it needs to go but we haven't agreed on what t= o >>>> tell INFRA regarding https://issues.apache.org/jira/browse/INFRA-4699. >>>>=20 >>>> I'm not really sure where to go from here. >>>=20 >>> Me either :-| >>>=20 >>> Lets sum up what we have now: >>> - log4j1 does "mvn site" to localhost and then commits the generated >>> file to svn trunk. =46rom there it will be taken with "svn up". This >>> process does not work well with pubsub because changes are visible >>> instantly. It needs to be changed. >>>=20 >>> - log4j2 seem to do everything locally and just upload the generated >>> files to either a staging folder or the real folder. This is my >>> preferred approach >>>=20 >>> - log4php does it (if i remember correctly) like log4j2 >>>=20 >>> - I don't know bout the other logging sites. >>>=20 >>> - Infra wants to see svnpubsub in action or that we use the CMS >>>=20 >>>=20 >>> Honestly my preferred approach is to have the rules in place you >>> mentioned in the issue. Ivans new main site is so simple, it really >>> does not need a CMS. The other pages should be taken with maven, as >>> usual. >>>=20 >>> That being said, it seems there is a maven plugin which works with the >>> CMS. Even when I really have no fun trying out the CMS, we might ask >>> if we can get some kind of a sandbox to try it out. Probably we can >>> work as we always did and we don't need to use the CMS interface >>> directly. >>>=20 >>> If we can use the CMS, we need to touch all pom files to enable it. >>> Basically it looks pretty straightforward, just moving the site-folder >>> to $project/content >>>=20 >>> So, how about asking about getting access to a sandbox CMS and trying >>> the maven build? >>>=20 >>> Cheers >>> Christian >>>=20 >>>=20 >>>=20 >>>>=20 >>>> Ralph >>>>=20 >>>> On May 2, 2012, at 2:11 AM, Ivan Habunek wrote: >>>>=20 >>>> Hi all, >>>>=20 >>>> I was away for a bit so I didn't comment earlier. >>>>=20 >>>> My idea is to generate the site using Twig [1], a nice PHP templating >>>> engine, in combination with Textile markup [2], which is much more vers= atile >>>> than most other common markup languages (such as markdown, apt, ...). >>>>=20 >>>> I have already converted the logging web site. The code can be found he= re: >>>> http://svn.apache.org/repos/asf/logging/site/branches/experimental-twig= -textile/ >>>>=20 >>>> And I have deployed the generated web for demo here: >>>> http://bezdomni.net/logging/ >>>>=20 >>>> This idea is obviously not compatible with the Apache CMS solution. Fra= nkly, >>>> I would prefer this solution to the CMS since, from what I have seen, t= he >>>> CMS is quite a pain to use. >>>>=20 >>>> Regards, >>>> Ivan >>>>=20 >>>> [1] http://twig.sensiolabs.org/ >>>> [2] http://textile.sitemonks.com/ >>>>=20 >>>>=20 >>>> On 2 May 2012 10:44, Christian Grobmeier wrote: >>>>>=20 >>>>> On Mon, Apr 23, 2012 at 4:06 AM, Ralph Goers >>>>> wrote: >>>>>>=20 >>>>>> On Apr 20, 2012, at 12:14 PM, Christian Grobmeier wrote: >>>>>>=20 >>>>>>=20 >>>>>> What i thought was, why not to clean it up? Your proposed solutions >>>>>> seem to be the cleanest way and updating everything just when we need= >>>>>> an update to the main site feels somehow wrong >>>>>>=20 >>>>>>=20 >>>>>> Joe has now proposed using the CMS for the main Logging web site alon= g >>>>>> with expaths.txt + svnpubsub for each sub-project. Each sub-project >>>>>> would >>>>>> then use svn externals so they could be independently managed. This >>>>>> sounds >>>>>> perfect to me. >>>>>=20 >>>>> OK I understand svn externals is like "symlinks for svn". Sounds ok. >>>>>=20 >>>>> I am a bit concerned on the CMS. Ivan has put much effort in the websi= te >>>>> design: >>>>>=20 >>>>> http://svn.apache.org/repos/asf/logging/site/branches/experimental-red= esign/src/site/pages/ >>>>>=20 >>>>> I will ask infra (on the ticket) if it is possible to either use that >>>>> design for the CMS or if we can bypass the CMS feature for this one >>>>> too... >>>>>=20 >>>>> Cheers >>>>> Christian >>>>>=20 >>>>>=20 >>>>>> Ralph >>>>>=20 >>>>>=20 >>>>>=20 >>>>> -- >>>>> http://www.grobmeier.de >>>>> https://www.timeandbill.de >>>>=20 >>>>=20 >>>>=20 >>>=20 >>>=20 >>>=20 >>> -- >>> http://www.grobmeier.de >>> https://www.timeandbill.de >>=20 >>=20 >>=20 >> --=20 >> http://www.grobmeier.de >> https://www.timeandbill.de