forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Crossley <>
Subject Re: xml-fop Build Failed
Date Fri, 23 Jul 2004 06:28:29 GMT
Clay Leeds wrote:
> David Crossley wrote
> > Clay Leeds wrote:
> >> David Crossley wrote:
> >>
> >>> Are you aware of issues FOR-202 and FOR-198? However, i see
> >>> by your build messages that you have not yet reached that stage.
> >>
> >> I'd seen those, but as you noticed, I hadn't gotten those errors, as I
> >> haven't gotten to that stage.
> >>
> >> UPDATE: I actually got the error specified by FOR-202 (it just hung 
> >> and
> >> I had to abort). I followed the instructions, and it seems to be
> >> working better than before, although I still get a  BUILD FAILED at 
> >> the end...

As the message says before Cocoon starts, if there is even just
one document broken, then you will get build failed. The other
docs are still generated though.

> >> p.s. Since I replaced the sitemap.xmap, I'm sure there will be some
> >> items missing. Although I added the 'FOP Additions', there are 
> >> probably
> >> other items that need to be added to accommodate for various included
> >> files:
> >> - xml-fop/src/documentation/content/xdocs/fo/*.fo
> >> - xml-fop/src/documentation/content/xdocs/dev/fo/*.fo
> >> - xml-fop/src/documentation/content/xdocs/dev/svg/*.svg
> >> ...etc.
> >
> > Not sure about the *.fo ... What processing do you intend to
> > happen for those?
> None, actually. Does this mean I should place the *.fo & *.svg files 
> (all of which need to remain in 'source' version) in:
>    src/documentation/resources/

They need to go as "raw content" into src/document/resources/content

That would mean that those matches in your sitemap
for fo/*.fo etc. could all be removed then.

> > One thing to bear in mind. Try to let Forrest do as much
> > work as possible by default. Only over-ride stuff when you
> > really must. Use grep in the src/core/context directory to
> > find certain matches.
> Can you give an example of how to use grep to accomplish what you're 
> talking about?

For example, if you want to find out how the "SVG to PNG" operates ...
cd src/core/context
grep png *.xmap
... there will be matches for two files. Look at sitemap.xmap first,
then at the one that it calls: resources.xmap
Use search function of your editor to find the matches that deal
with "png".

> >> I'm not sure if I should wait for a reply on this before I
> >> start working to resolve issues (as forrest-devs are more likely to
> >> spot 'glaring' issues than I am). I did notice differences in the old
> >> and new versions of sitemap.xmap with regard to pipelines for *.fo,
> >> *.svg, although I haven't taken the time to completely comprehend what
> >> those differences mean.
> >>
> >>> <><><><>< FORREST OUTPUT ><><><><><
> >>
> >> [clay@Clays-TiBook xml-fop]$ forrest -Dskip.contentcheck=yes seed
> >> Apache Forrest.  Run 'forrest -projecthelp' to list options
> >
> > Why are you skipping the content-check part?
> >
> > Whoa, stop.
> >
> > Unless i am reading the following output incorrectly
> > you are seeding a new project over the top of your
> > existing FOP website source. That is why the
> > "context-check" is done ... to prevent such accidents.
> Yeah... That was foolish. I misunderstood the 'seed' function. Heh.
> Is  it correct to assume that running 'forrest seed' (without 
> '-Dskip.contentcheck=yes'!) copies the original files for everything 
> (except the src/ dir)?

You could experiment in a spare directory. I just tried
and it seems that without the "-Dskip.contentcheck=yes"
you will get an immediate failure, so as to stop any accident.
Using the "-Dskip.contentcheck=yes" to proceed anyway, then
any missing files are added, but existing ones are not touched.


Anyway, yes it only needs to be done once to set up the project.

However, you will probably have some spare files in your project
that you would remove manually. (Compare with a new forrest seed.)

David Crossley

View raw message