From dev-return-12839-apmail-forrest-dev-archive=forrest.apache.org@forrest.apache.org Wed Oct 20 18:55:07 2004 Return-Path: Delivered-To: apmail-forrest-dev-archive@www.apache.org Received: (qmail 35129 invoked from network); 20 Oct 2004 18:55:07 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 20 Oct 2004 18:55:07 -0000 Received: (qmail 72328 invoked by uid 500); 20 Oct 2004 18:55:05 -0000 Delivered-To: apmail-forrest-dev-archive@forrest.apache.org Received: (qmail 72277 invoked by uid 500); 20 Oct 2004 18:55:04 -0000 Mailing-List: contact dev-help@forrest.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: dev@forrest.apache.org Delivered-To: mailing list dev@forrest.apache.org Received: (qmail 72264 invoked by uid 99); 20 Oct 2004 18:55:04 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: local policy) Received: from [65.104.121.53] (HELO mail.medata.com) (65.104.121.53) by apache.org (qpsmtpd/0.28) with ESMTP; Wed, 20 Oct 2004 11:55:03 -0700 Received: from [172.24.2.66] ([172.24.2.66]) (authenticated bits=0) by mail.medata.com (8.12.8/8.12.8) with ESMTP id i9KIsv91026903 for ; Wed, 20 Oct 2004 11:54:59 -0700 Mime-Version: 1.0 (Apple Message framework v619) In-Reply-To: <4176A3F8.8050707@apache.org> References: <0ABB57CE-DADD-11D8-8DCA-00039385397E@medata.com> <78D5CBC0-E182-11D8-A85F-00039385397E@medata.com> <599A46F4-E23A-11D8-B3AB-00039385397E@medata.com> <8C2FD019-E242-11D8-B3AB-00039385397E@medata.com> <410A8D7B.9030203@brondsema.net> <410D53A3.8060702@brondsema.net> <65E128D6-E4B7-11D8-BA09-00039385397E@medata.com> <41101B0D.9040408@brondsema.net> <1EC1B9E7-2193-11D9-9F59-00039385397E@medata.com> <41755! 5E7.7080501@che-che.com> <5511786E-21FE-11D9-B68A-00039385397E@medata.com> <417567F1.1080503@che-che.com> <4176181E.50! 60403@che-che.com> <4176A3F8.8050! 707@apache.org> Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed Message-Id: <8581CBDD-22C9-11D9-9D56-00039385397E@medata.com> Content-Transfer-Encoding: quoted-printable From: Clay Leeds Subject: Re: xml-fop Build Failed Date: Wed, 20 Oct 2004 11:54:50 -0700 To: dev@forrest.apache.org X-Mailer: Apple Mail (2.619) X-Virus-Scanned: ClamAV 0.80rc4/532/Fri Oct 15 11:22:57 2004 clamav-milter version 0.80j on mail.medata.com X-Virus-Status: Clean X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N On Oct 20, 2004, at 10:44 AM, Juan Jose Pablos wrote: > Clay Leeds wrote: >>> So >>> 1) I will upgrade fop-0.20.5.jar and batik-all-1.5.1.jar from the =20= >>> cocoon-2.2.0-dev tree in the next hour unless someone has any =20 >>> objection. >> Will I need to do that as well? > > Well you need to get the latest copy from forrest svn. I'll get the latest forrest from svn. Thanks! >>> 2) Clay >>> Please apply this patch and upgrade to the svn version >> Wouldn't it be the other way around (/svn up/ and then apply the =20 >> PATCH?)? > > This patch is for the xml-fop cvs. ok. I was confused, because you said apply this patch and upgrade to =20 the svn version... as you indicate, xml-fop uses cvs, and forrest uses =20= svn... All these projects make it confusing to me to know what to fix =20= (although the fact that it's called fix4fop.diff should've been a =20 clue!) >>> (you need to create an empty site.xml for this to work. >> That seems strange, as my site.xml file has tons in it. Forgive my =20= >> question, but what is the purpose of an empty site.xml file? > > =BF? > Are we talking about the same site? > I did check the problem on a copy of the xml-fop. Are we usinng the =20= > same one? Nope. I've practically given up on the xml-fop xdocs/*.xml (and subdir =20= *.xml files). My plan (which may be a bad plan!) was to start from the =20= xml-fop_new.zip file referenced in this POST[1] (link [2] from that =20 post). Obviously, I would rather work with the xml-fop cvs files, but Dave =20 Brondsema's instructions dealt with link [2] from that post. I suppose =20= that those instructions might be able to work from xml-fop cvs, though. =20= If so (or I could get new instructions which work with xml-fop cvs), =20 that would be great and would save me a step or two! Oh what a tangled web we weave... when we try and figure out all this =20= stuff and it takes months to learn! >>> Cheers, >>> Cheche >>> [1] http://issues.apache.org/eyebrowse/ReadMsg?=20 listName=3Ddev@forrest.apache.org&msgNo=3D14532 Web Maestro Clay --=20 Clay Leeds - Webmaster/Developer - Medata, Inc. - PGP Public Key: