Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 36378 invoked by uid 500); 23 Nov 2001 15:20:28 -0000 Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-dev@xml.apache.org Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 36352 invoked from network); 23 Nov 2001 15:20:27 -0000 Content-Type: text/plain; charset="iso-8859-1" From: David Crossley Reply-To: crossley@indexgeo.com.au To: cocoon-dev@xml.apache.org Subject: Re: Compilation problems was RE: [Fwd: freshmeat project listing for Cocoon] Date: Sat, 24 Nov 2001 02:22:16 +1100 X-Mailer: KMail [version 1.2] References:

<20011123142131.D3182@bremen.dvs1.informatik.tu-darmstadt.de> In-Reply-To: <20011123142131.D3182@bremen.dvs1.informatik.tu-darmstadt.de> MIME-Version: 1.0 Message-Id: <01112402221600.00960@igacer> Content-Transfer-Encoding: 8bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Christian Haul wrote: > On 23.Nov.2001 -- 01:43 PM, giacomo wrote: > > On Fri, 23 Nov 2001, Carsten Ziegeler wrote: > > > > From: giacomo [mailto:giacomo@apache.org] > > > > Big no. After a clean checkout of the HEAD I was able to compile > > > > but building the docs failed havily. > > > > > > > > Could someone fix that more familiar with it than I am? I think it has > > > > to do with the DTD resolver whcih cannot find the DTDs requested during > > > > the build of the docs (even if I've sound them to be there where it > > > > complains wouldn't be there). > > > a "build docs" works perfectly here. Hm > > > > Lucky you. This is what I get on a clean checkout from HEAD: > > > > INFO 10065 [ ] (): Link translated: > > graphics/Todo-label_over.jpg > > Resolved public: -//APACHE//DTD Documentation V1.0//EN > > > > file://home/giacomo/cvs/xml-cocoon2/build/cocoon/documentation/resources/entities/document-v10.dtd > > Failed to create InputSource: > > file://home/giacomo/cvs/xml-cocoon2/build/cocoon/documentation/resources/entities/document-v10.dtd > > ERROR 10065 [ ] (): Could not read resource > > file:/home/giacomo/cvs/xml-cocoon2/build/cocoon/documentation/xdocs/plan/index.xml > > org.xml.sax.SAXParseException: File > > "file:/home/giacomo/cvs/xml-cocoon2/build/cocoon/documentation/dtd/document-v10.dtd" > > not found. > > For me "build docs" fails to find the catalogs, too. > > I *think* it should be "file:///home/g..." (3 x '/'). If you point > e.g. w3m or mozilla to the modified URL it will find the file. > > For cocoon_20_branch applying > > --- documentation/cocoon.xconf.orig Mon Nov 19 11:12:58 2001 > +++ documentation/cocoon.xconf Thu Nov 22 14:53:48 2001 > @@ -101,7 +101,7 @@ > > --> > > - > + > > > > resolves :-) the issue for me. Alternatively, value="resources..." > works OK as well. Looks like the URL is not composed correctly. > BTW: this is linux with sun jdk 1.3.1 I did raise this issue a long time ago. Everyone said that the docs build worked for them. So i thought that it was only my problem. Now it looks like i have company. Yes Christian, i too am on Linux with Blackdown J2SDK 1.3.0 My workaround is a bit different - i add a hard-coded path into build.xml for the docs target build context (to replace arg -c current dir). So why would this just happen for Linux. The path to the catalog is being built in components/resolver/ResolverImpl.java line 97: String catalogURL = this.context.getResource(catalogFile).toExternalForm(); Here is the previous discussion about this file:// problem ... http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=100376303909599&w=2 (By the way what does this issue have to do with Freshmeat. Please use sensible Subjects.) --David --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org