Re: Building site with forrest
Correction:
On Jul 28, 2004, at 1:33 PM, Clay Leeds wrote:
2. Files in build/webapps/content are missing. These problems can be
solved
by copying src/documentation/content into webapps, or by replacing
in sitemap-0.5.xmap all source references to content/ with
{project:content}, whatever that may mean.
I don't recall why a sitemap-0.5.xmap was created, but I removed it
completely.
It is still in our CVS repository. And it is the sitemap which forrest
uses in my local build.
True. I didn't remove it from CVS. I removed it from my local copy at
the request of the forrest-dev folks who were helping me. In fact, I
eradicated both sitemap*.xmap files from my local directory.
I eradicated them, then grabbed a fresh copy and re-inserted the ===
FOP ADDITIONS === section.
Web Maestro Clay
Re: Building site with forrest
On Jul 28, 2004, at 11:47 AM, Simon Pepping wrote:
On Sun, Jul 25, 2004 at 12:46:03PM -0700, Clay Leeds wrote:
(More comments inline)
On Jul 25, 2004, at 11:41 AM, Simon Pepping wrote:
I have tried to build the site with forrest, without much success. I
had a few problems:
1. Validation error. I solved this problem by creating an OASIS
catalog.
I solved this by essentially replacing the xml-fop/.../sitemap.xmap
file with a 'clean' version from forrest. I then added the FOP
ADDITIONS section.
When online, validation succeeds because the system ids point to the
CVS. Offline, most validation succeeds due to forrest's catalog, which
points to local copies of the DTDs. This does not work for
compliance.xml, which uses its own DTD. There is an SGML Open Catalog
for it, but apparently that is not used. I added an OASIS XML catalog,
and now the local copy of the DTD in my CVS working directory is used.
I'd like to figure out how to do that. I'm using eclipse for much of my
editing...
2. Files in build/webapps/content are missing. These problems can be
solved
by copying src/documentation/content into webapps, or by replacing
in sitemap-0.5.xmap all source references to content/ with
{project:content}, whatever that may mean.
I don't recall why a sitemap-0.5.xmap was created, but I removed it
completely.
It is still in our CVS repository. And it is the sitemap which forrest
uses in my local build.
True. I didn't remove it from CVS. I removed it from my local copy at
the request of the forrest-dev folks who were helping me. In fact, I
eradicated both sitemap*.xmap files from my local directory.
My plan (when I get Forrest building successfully!) is to replace all
forrest-related files (forrest.properties, site.xml, sitemap.xmap,
etc.) and eradicate those which are not needed (sitemap-0.5.xmap, as
well as all of those book.xml files--these are all replaced by
site.xml--unless there's a compelling reason for them).
Regards, Simon
Thanks for the message. I'm looking forward to getting the forrest
stuff *&* your documentation files in xml-fop!
Web Maestro Clay
Re: Building site with forrest
Clay,
Thanks for your reply.
On Sun, Jul 25, 2004 at 12:46:03PM -0700, Clay Leeds wrote:
> Simon,
>
> I have been working at getting the xml-fop web site working for many
> months (at first using forrest-0.5.1, and more recently with
> forrest-0.6 since they're about to release a new version). More
> recently, I've had some success, but I'm currently working with the
> forrest-dev list to get them resolved--and we've made progress[1] &
> [1a].
I appreciate that that is not an easy problem to solve.
> (More comments inline)
>
> On Jul 25, 2004, at 11:41 AM, Simon Pepping wrote:
> >I have tried to build the site with forrest, without much success. I
> >had a few problems:
> >
> >1. Validation error. I solved this problem by creating an OASIS
> >catalog.
>
> I solved this by essentially replacing the xml-fop/.../sitemap.xmap
> file with a 'clean' version from forrest. I then added the FOP
> ADDITIONS section.
When online, validation succeeds because the system ids point to the
CVS. Offline, most validation succeeds due to forrest's catalog, which
points to local copies of the DTDs. This does not work for
compliance.xml, which uses its own DTD. There is an SGML Open Catalog
for it, but apparently that is not used. I added an OASIS XML catalog,
and now the local copy of the DTD in my CVS working directory is used.
> >2. Files in build/webapps/content are missing. These problems can be
> >solved
> > by copying src/documentation/content into webapps, or by replacing
> > in sitemap-0.5.xmap all source references to content/ with
> > {project:content}, whatever that may mean.
>
> I don't recall why a sitemap-0.5.xmap was created, but I removed it
> completely.
It is still in our CVS repository. And it is the sitemap which forrest
uses in my local build.
Regards, Simon
--
Simon Pepping
home page: http://www.leverkruid.nl
Re: Building site with forrest
Simon,
I have been working at getting the xml-fop web site working for many
months (at first using forrest-0.5.1, and more recently with
forrest-0.6 since they're about to release a new version). More
recently, I've had some success, but I'm currently working with the
forrest-dev list to get them resolved--and we've made progress[1] &
[1a].
(More comments inline)
On Jul 25, 2004, at 11:41 AM, Simon Pepping wrote:
I have tried to build the site with forrest, without much success. I
had a few problems:
1. Validation error. I solved this problem by creating an OASIS
catalog.
I solved this by essentially replacing the xml-fop/.../sitemap.xmap
file with a 'clean' version from forrest. I then added the FOP
ADDITIONS section.
2. Files in build/webapps/content are missing. These problems can be
solved
by copying src/documentation/content into webapps, or by replacing
in sitemap-0.5.xmap all source references to content/ with
{project:content}, whatever that may mean.
I don't recall why a sitemap-0.5.xmap was created, but I removed it
completely.
3. File src/documentation/content/xdocs/site.xml is missing. I did not
solve that problem.
I have a few files here you can play with[2].
I've solved many of the errors, although I still get BUILD errors too.
At this point, the errors seem to be mostly due to our having .svg &
.fo files in the xml-fop/dev/svg/, xml-fop/dev/fo/, and xml-fop/fo/
directories, which need to be added to the sitemap.xmap pipeline.
Building the target htmldoc causes even more errors.
Are these two indeed broken, or am I doing something wrong?
I have been focusing on getting the site to build correctly[3]. Once
I've gotten that completed my intention is to turn my attention to
javasrc/JXR & htmldoc.
Regards, Simon
--
Simon Pepping
home page: http://www.leverkruid.nl
Cheers,
Web Maestro Clay
p.s. Many apologies that the xml-fop site hasn't moved to the next
level yet. It has taken me a long time to get as far as I have (many
months), and I'm finally getting somewhere. I'm hoping we won't have to
wait until the forrest-0.6 release, as progress is moving along on
resolution. xml-fop's forrest-related files (site.xml,
forrest.properties, sitemap.xmap, etc.) had lots of antiquated code/XML
that needed to be removed and then reconciled (for lack of a better
term) with advanced features that were added. Some of these were
causing the validation errors--especially if you're trying to use the
newer versions like 0.5.x & 0.6.
[1] 2004-07-21 xml-fop Build Failed (was Re: Forrest skins...) Clay
Leeds
http://marc.theaimsgroup.com/?l=forrest-dev&m=109039040919791&w=2
[1a] 2004-07-22 Re: xml-fop Build Failed (*renamed thread*) David
Crossley
http://marc.theaimsgroup.com/?l=forrest-dev&m=109047842223058&w=2
[2] a few key files
http://homepage.mac.com/webmaestro/xml-fop/xml-fop_files.zip
[3] xml-fop web site w/ new logo (very rough).
http://homepage.mac.com/webmaestro/xml-fop/
Building site with forrest
I have tried to build the site with forrest, without much success. I
had a few problems:
1. Validation error. I solved this problem by creating an OASIS catalog.
2. Files in build/webapps/content are missing. These problems can be solved
by copying src/documentation/content into webapps, or by replacing
in sitemap-0.5.xmap all source references to content/ with
{project:content}, whatever that may mean.
3. File src/documentation/content/xdocs/site.xml is missing. I did not
solve that problem.
Building the target htmldoc causes even more errors.
Are these two indeed broken, or am I doing something wrong?
Regards, Simon
--
Simon Pepping
home page: http://www.leverkruid.nl
