Tony Collen wrote: > Hi everybody, > > In my never-ending quest to get the cocoon docs built with forrest, > I've recently downloaded forrest-0.5.1-bin. I am now slightly > further ahead than last time when I had some problems. Here's > the output of my build (current CVS co): > > > ==== > > * [25] 1.192s 56.1Kb userdocs/advanced/authentication/authentication.html > * [0] 2.063s 52.2Kb userdocs/advanced/authentication/authentication.pdf > Total time: 7 minutes 25 seconds > BUILD FAILED > C:\tcollen\dev\xml-forrest\forrest.build.xml:631: Java returned: 1 > Total time: 8 minutes 2 seconds > > BUILD FAILED > file:C:/tcollen/dev/xml-forrest/forrest.antproxy.xml:45: Java returned: 1 > > Total time: 10 minutes 1 second > > ==== > > Any Forrest people have some hints? There is no stack trace, and it seems to be > building the docs > with Forrest just fine until it gets to the end. > > Frustrated, yet continuing on,
There was a broken link reported during the build. I think that that is why we get a "build failed" message at the end. Otherwise the docs are all built properly. What the build neglected to say, was that you should do ... cat build/cocoon-2.1.3-dev/tmp/brokenlinks.xml <broken-links> <link message="No pipeline matched request: plan/changes.rss">plan/changes.rss</link> </broken-links> Now here is a laugh (or the ultimate cry of frustration) ... You do get that vital hint if there are *no* broken links. Is that a Cocoon CLI bug or a Forrest bug? --David
