From general-return-1852-apmail-logging-general-archive=logging.apache.org@logging.apache.org Mon Jun 11 17:18:40 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 08CA39F9A for ; Mon, 11 Jun 2012 17:18:40 +0000 (UTC) Received: (qmail 87361 invoked by uid 500); 11 Jun 2012 17:18:39 -0000 Delivered-To: apmail-logging-general-archive@logging.apache.org Received: (qmail 87281 invoked by uid 500); 11 Jun 2012 17:18: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 87271 invoked by uid 99); 11 Jun 2012 17:18:39 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 11 Jun 2012 17:18:39 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,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; Mon, 11 Jun 2012 17:18:30 +0000 Received: by dalh21 with SMTP id h21so5244283dal.34 for ; Mon, 11 Jun 2012 10:18:09 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=from:mime-version:content-type:subject:date:in-reply-to:to :references:message-id:x-mailer:x-gm-message-state; bh=KdhJMMS4RVPBR4oKvLFomm3UNnQW+mPd6SpRN8bYAgk=; b=R3MnN+R4tH2wvrcKB8cKhLQmTke4nLs9ZgOh3Wj5BN8iTFh2WYcFnNSKrQJfG1u3XY ImM+NXOvrndKQCIfcQ4Ieq0lsNz6qvUDN2X9Qd+5ZijjJVRabH0Dk/8mfMCRjrPP7680 6idjaDriq2s1cT32PfvGCEX+mjSksl0vEzp4yYlUIQqJJxMrKQ6NkMxrWOMC6swmBhSh O4+fS7peM2pi5PqNYbJfhqMk83pfSx+5wIXEH9eeEnCBfpxkDC7N/FfjO09xpxi2hgmj 6MDY/l0cnfDWg/Nm+mF/ltL16x8T1EWIdpM6zikKav8ToUmEgJxOnowB+ka6Q9ZTLDhn bI/A== Received: by 10.68.204.2 with SMTP id ku2mr28757366pbc.55.1339435088885; Mon, 11 Jun 2012 10:18:08 -0700 (PDT) Received: from [172.28.240.61] (charger.intuit.com. [208.240.243.170]) by mx.google.com with ESMTPS id ub8sm19072793pbc.44.2012.06.11.10.18.07 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 11 Jun 2012 10:18:08 -0700 (PDT) From: Ralph Goers Mime-Version: 1.0 (Apple Message framework v1278) Content-Type: multipart/alternative; boundary="Apple-Mail=_18B28A27-DDA5-4DA5-ACC1-8F8296720BF9" Subject: Re: Steps for Producr Sites? (was Re: Logging web sites) Date: Mon, 11 Jun 2012 10:18:07 -0700 In-Reply-To: To: Logging General References: <7F1F7665-D82D-4374-988C-F400A3610205@dslextreme.com> <2292772.PvrqEaSf2C@bigmax> <25272074.tCi0icyh1W@bigmax> <0D743CB6-8893-4FAF-86CD-1809B4E77F1C@dslextreme.com> <8762azy17o.fsf_-_@v35516.1blu.de> Message-Id: <20AA392B-C76F-4932-BA88-CBDAD5CD66E4@dslextreme.com> X-Mailer: Apple Mail (2.1278) X-Gm-Message-State: ALoCoQnDklVLRp/EXsX7BzidEoTkdZs3D7kO90Pw2rvSoBHK/Dfb9tQLkggXeWd8gNQXr1QZ2EVT --Apple-Mail=_18B28A27-DDA5-4DA5-ACC1-8F8296720BF9 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii See http://wiki.apache.org/logging/ManagingTheWebSite Ralph On Jun 10, 2012, at 8:58 AM, Ralph Goers wrote: > I plan to document this on the wiki when I get home later today. The = process isn't quite as you have listed. =20 >=20 > 1. Check out the production web site. > 2. Create a log4xxx directory adjacent to the log4j directory, > 3. Underneath that directory create a directory for the releases of = the component such as log4xxx-1.8. > 4. Copy the release website into that directory. > 5. In your log4xxx directory create a symlink of 1.x to log4xxx-1.8. = "ln -s log4xxx-1.8 1.x" on a Mac or unix system. Windows doesn't support = links afaik. > 6. Make sure all that is added to svn and commit it. > 7. In the main web site check that index.twig and the navbar template = reference your component as "log4xxx/1.x". > 8. Unindent your component in extpaths.txt.=20 >=20 > If you want to use the CMS directly it is certainly easy to do. >=20 > Sent from my iPad >=20 > On Jun 10, 2012, at 2:18 AM, Stefan Bodewig = wrote: >=20 >> Hi all, >>=20 >> On 2012-06-10, Ralph Goers wrote: >>=20 >>> We really don't need to use the maven publish plugin as I've checked >>> in the each project in its own release directly and then used a >>> symlink to point the project site to the specific release. Each of >>> the other sub-sites should do the same thing. >>=20 >> I missed most of the thread, been busy elsewhere, sorry. I'd like to >> add log4net to the site "the right way", what do I need to do? >>=20 >> This is my understanding >>=20 >> (1) check in the log4net site wherever I want >>=20 >> (2) create a symlink from where I commited the site to = content/log4net >>=20 >> (3) un-indent log4net in extpath.txt >>=20 >> Is this correct? >>=20 >> Problems I currently see: >>=20 >> * the log4net site is generated by Maven and has inconsistent = line-ends, >> is there any better way than Ant's fixcrlf task to fix that? Our >> build already includes NAnt and Maven, I'd prefer to avoid adding a >> third build tool 8-) >>=20 >> Mid-term log4net may be better off using the CMS directly, but that's >> something we need to discuss. >>=20 >> * I don't know how and where to perform step (2) from above. >>=20 >> Stefan --Apple-Mail=_18B28A27-DDA5-4DA5-ACC1-8F8296720BF9 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii http://wiki.apa= che.org/logging/ManagingTheWebSite

Ralph
On Jun 10, 2012, at 8:58 AM, Ralph Goers wrote:

I = plan to document this on the wiki when I get home later today. The = process isn't quite as you have listed.  

1. Check out the = production web site.
2. Create a log4xxx directory adjacent to the = log4j directory,
3. Underneath that directory create a directory for = the releases of the component such as log4xxx-1.8.
4. Copy the = release website into that directory.
5. In your log4xxx directory = create a symlink of 1.x to log4xxx-1.8. "ln -s log4xxx-1.8 1.x" on a Mac = or unix system. Windows doesn't support links afaik.
6. Make sure all = that is added to svn and commit it.
7. In the main web site check = that index.twig and the navbar template reference your component as = "log4xxx/1.x".
8. Unindent your component in extpaths.txt.

If = you want to use the CMS directly it is certainly easy to do.

Sent = from my iPad

On Jun 10, 2012, at 2:18 AM, Stefan Bodewig <bodewig@apache.org> = wrote:

Hi = all,

On 2012-06-10, = Ralph Goers wrote:

We really don't need to use the maven publish plugin as = I've checked
in the each project in its own = release directly and then used = a
symlink to point the project site to the specific release. =  Each of
the other sub-sites should do = the same thing.

I missed most = of the thread, been busy elsewhere, sorry.  I'd like = to
add log4net to the site = "the right way", what do I need to do?

This is my = understanding

(1) check in = the log4net site wherever I want

(2) create a = symlink from where I commited the site to = content/log4net

(3) un-indent = log4net in extpath.txt

Is this = correct?

Problems I = currently see:

* the log4net = site is generated by Maven and has inconsistent = line-ends,
is there any = better way than Ant's fixcrlf task to fix that? =  Our
build already = includes NAnt and Maven, I'd prefer to avoid adding = a
third build tool = 8-)

Mid-term log4net may be better off using the CMS = directly, but that's
= something we need to discuss.

* I don't know = how and where to perform step (2) from = above.

Stefan

<= /html>= --Apple-Mail=_18B28A27-DDA5-4DA5-ACC1-8F8296720BF9--