forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Crossley <cross...@apache.org>
Subject Re: xml-fop Compliance Page (was Re: xml-fop Build Failed)
Date Tue, 09 Nov 2004 00:14:03 GMT
Clay Leeds wrote:
> Juan Jose Pablos wrote:
> > David Crossley wrote:
> >> Juan Jose Pablos wrote:
> >>> The only work around this was to add a catalog using the 
> >>> CatalogManager.properties.
> >> Correct. That file is required. It is not a "work around",
> >> it is required.
> >
> > If you have ${project.content-dir}/classes/CatalogManager.properties
> >
> > You must add relative-catalogs=false and a relative path on catalogs 
> > i.e:
> >
> > relative-catalogs=false
> > catalogs=../resources/schema/catalog.xcat
> 
> The version of CatalogManager.properties that was committed last night 
> is what you sent me, Cheche (thanks!). The only lines which are not 
> commented out are:
> 
> [..]
> verbosity=10
> [..]
> catalogs=../resources/schema/catalog.xcat
> relative-catalogs=false

As i said before, don't leave that settting
at "verbosity=10" or you will get swamped with messages.
It is just for testing that your catalog entity resolver
is finding your compliance.dtd properly.

-- 
David Crossley


Mime
View raw message