From general-return-1841-apmail-logging-general-archive=logging.apache.org@logging.apache.org Sun Jun 10 09:18:52 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 06C26C2AF for ; Sun, 10 Jun 2012 09:18:52 +0000 (UTC) Received: (qmail 97354 invoked by uid 500); 10 Jun 2012 09:18:51 -0000 Delivered-To: apmail-logging-general-archive@logging.apache.org Received: (qmail 97204 invoked by uid 500); 10 Jun 2012 09:18: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 97172 invoked by uid 99); 10 Jun 2012 09:18:49 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 10 Jun 2012 09:18:49 +0000 X-ASF-Spam-Status: No, hits=0.7 required=5.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [88.84.128.168] (HELO samaflost.de) (88.84.128.168) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 10 Jun 2012 09:18:41 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by samaflost.de (Postfix) with ESMTP id 63E22289800B for ; Sun, 10 Jun 2012 11:18:20 +0200 (CEST) Received: from samaflost.de ([127.0.0.1]) by localhost (v35516.1blu.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7E4sQqBN7dKx for ; Sun, 10 Jun 2012 11:18:19 +0200 (CEST) Received: by samaflost.de (Postfix, from userid 1000) id EDD9E2898013; Sun, 10 Jun 2012 11:18:19 +0200 (CEST) From: Stefan Bodewig To: "Logging General" Subject: Steps for Producr Sites? (was Re: Logging web sites) References: <7F1F7665-D82D-4374-988C-F400A3610205@dslextreme.com> <2292772.PvrqEaSf2C@bigmax> <25272074.tCi0icyh1W@bigmax> <0D743CB6-8893-4FAF-86CD-1809B4E77F1C@dslextreme.com> Date: Sun, 10 Jun 2012 11:18:19 +0200 In-Reply-To: <0D743CB6-8893-4FAF-86CD-1809B4E77F1C@dslextreme.com> (Ralph Goers's message of "Sat, 9 Jun 2012 15:31:36 -0700") Message-ID: <8762azy17o.fsf_-_@v35516.1blu.de> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii 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