Return-Path: Delivered-To: apmail-xml-forrest-dev-archive@www.apache.org Received: (qmail 69757 invoked from network); 11 Mar 2004 15:35:25 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 11 Mar 2004 15:35:25 -0000 Received: (qmail 55717 invoked by uid 500); 11 Mar 2004 15:35:12 -0000 Delivered-To: apmail-xml-forrest-dev-archive@xml.apache.org Received: (qmail 55667 invoked by uid 500); 11 Mar 2004 15:35:12 -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 55622 invoked from network); 11 Mar 2004 15:35:12 -0000 Received: from unknown (HELO mx1.try.sybase.com) (130.214.10.19) by daedalus.apache.org with SMTP; 11 Mar 2004 15:35:12 -0000 Received: from mail.try.sybase.com (mail.try.sybase.com [130.214.10.18]) by mx1.try.sybase.com (8.11.6/8.11.0) with ESMTP id i2BEX0201290 for ; Thu, 11 Mar 2004 07:33:00 -0700 Received: from tsws1 ([10.22.120.38]) by mail.try.sybase.com (8.11.6/8.11.6) with SMTP id i2BFH6k00636 for ; Thu, 11 Mar 2004 08:17:07 -0700 Message-ID: <021301c4077e$73b25fc0$0100a8c0@tsws1> From: "Adam R. B. Jack" To: Subject: forrest.validation.failonerror=false Date: Thu, 11 Mar 2004 08:35:04 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 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 Is there a way to get this behaviour, i.e. forrest merely skips bad pages, it doesn't fail & quit? I see in the status.xml it was added, but I don't get the desired behaviour (see below). [BTW: I only found this string in the status.xml, so I guess maybe it isn't enabled in any of the forrest scripts.] Just so you know, this is from Gump running builds and trying to document the build outputs into a source box. Much as Gump tries to escape everything, when somebody decided to cat the contents of a compressed file to the screen, things barfed. Much as I'll attempt to fix this, it'd be nice if the whole site didn't fail because of one page. BTW: Whilst I'm sending this, anybody know how if one can force 'wrap' (or fixed width) on a forrest -Dforrest.validation.failonerror=false [...] validate-xdocs: /var/gump/ws/forrest/src/documentation/content/xdocs/logging-log4j/gump_work /build_logging-log4j_log4j-tests.xml:3779:19: An invalid XML character (Unicode: 0x1f) was found in the element content of the document. BUILD FAILED /gump/forrest/forrest.build.xml:935: Could not validate document /var/gump/ws/forrest/src/documentation/content/xdocs/logging-log4j/gump_work /build_logging-log4j_log4j-tests.xml Thank in advance for any assistence. regards, Adam -- Experience the Unwired Enterprise: http://www.sybase.com/unwiredenterprise Try Sybase: http://www.try.sybase.com