Return-Path: Delivered-To: apmail-xml-forrest-dev-archive@www.apache.org Received: (qmail 1818 invoked from network); 30 Mar 2004 14:58:45 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 30 Mar 2004 14:58:45 -0000 Received: (qmail 54188 invoked by uid 500); 30 Mar 2004 14:58:29 -0000 Delivered-To: apmail-xml-forrest-dev-archive@xml.apache.org Received: (qmail 54139 invoked by uid 500); 30 Mar 2004 14:58:29 -0000 Mailing-List: contact forrest-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: forrest-dev@xml.apache.org Delivered-To: mailing list forrest-dev@xml.apache.org Received: (qmail 54068 invoked from network); 30 Mar 2004 14:58:28 -0000 Received: from unknown (HELO correo.asesoriaezequiel.com) (80.39.13.9) by daedalus.apache.org with SMTP; 30 Mar 2004 14:58:28 -0000 Received: from che-che.com (unknown [192.168.1.5]) by correo.asesoriaezequiel.com (Postfix) with ESMTP id 3328C15017 for ; Tue, 30 Mar 2004 16:58:15 +0200 (CEST) Message-ID: <40698AFC.6080305@che-che.com> Date: Tue, 30 Mar 2004 16:58:04 +0200 From: Juan Jose Pablos User-Agent: Mozilla/5.0 (X11; U; Linux i686; es-ES; rv:1.5) Gecko/20031107 Debian/1.5-3 X-Accept-Language: es, en MIME-Version: 1.0 To: forrest-dev@xml.apache.org Subject: Re: upgrading an existing forrest installation References: <200403301256.08761.rob.exley@equifax.com> In-Reply-To: <200403301256.08761.rob.exley@equifax.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Rob, > What is the recommended approach for upgrading an existing forrest > installation ? For people that use the SVN version, just remember to change your FORREST_HOME value. > I am in the process of using forrest for an internal documentation site and > having just updated my forrest build directory from SVN it now complains > about illegal attributes within the skinconf.xml file on the toc element. It complains about @level on the TOC element. It has been replace @max-depth. Now he have 2 options here: 1)allow the level attribute even it will not be used. 2) create a xsl file that convert old skin @level to be converted to @max-depth for 2, we need to have a @version on the skinconf. WDYT?