RE: [site docs] build failing
Nicola Ken Barozzi wrote: > > Carsten Ziegeler wrote: > > > Building the docs failed because plan/changes.rss could not > > be generated (no pipeline found). > > I just checked in a hack to the doc sitemap, so this pipeline > > is now found and building the docs, especially the site docs > > works again. > > > > Does anyone know where plan/changes.rss is used and why? > > Changes.rss is created from changes.xml by Forrest to give an RSS feed > from the changes. It's included in the changes.xml page as a link. > > See this as an example: > http://xml.apache.org/forrest/changes.html > > It's strange, is there no sitemap that does this in your forrest? wierd... > It was, but the incoming request is plan/changes.rss and we had a matcher for "**changes.rss" that forwarded this to the status sitemap that only matches against "changes.rss". As there request uri was passed on without any changes, the status sitemap didn't match. I changed the mount statemenet in our sitemap, so the value for "**" is removed and than it works but is obviously wrong. Carsten
Re: [site docs] build failing
Carsten Ziegeler wrote: Building the docs failed because plan/changes.rss could not be generated (no pipeline found). I just checked in a hack to the doc sitemap, so this pipeline is now found and building the docs, especially the site docs works again. Does anyone know where plan/changes.rss is used and why? Changes.rss is created from changes.xml by Forrest to give an RSS feed from the changes. It's included in the changes.xml page as a link. See this as an example: http://xml.apache.org/forrest/changes.html It's strange, is there no sitemap that does this in your forrest? wierd... -- Nicola Ken Barozzi [EMAIL PROTECTED] - verba volant, scripta manent - (discussions get forgotten, just code remains) -
RE: [site docs] build failing
Building the docs failed because plan/changes.rss could not be generated (no pipeline found). I just checked in a hack to the doc sitemap, so this pipeline is now found and building the docs, especially the site docs works again. Does anyone know where plan/changes.rss is used and why? Carsten
Re: [site docs] build failing
Upayavira wrote: > David Crossley wrote: > > >If you build a site that *has no* broken links, then you will get > >a successful build, and a reminder to check the broken links file. > > A reminder? I've never seen one. Is that provided by Forrest? Okay, it must be Forrest then. -- Please check the file /usr/local/cvs/cocoon-site/build/tmp/brokenlinks.xml for any broken links in the generated site. -- > >If you build a site that *does have* broken links, then you will get > >a mention of the broken link as it goes past, and a "build failed" > >message at the end. However there is no message to check the broken > >links file. > > Fair enough. The details at the bottom of a site generation do not > summarise the number of broken links. I'll add some kind of reporting of > that to my todo list. That would be good too. --David
RE: [site docs] build failing
Upayavira wrote: > Thinking about it - can't you do that in Ant? Tell it whether to > fail-on-error or not? > Hmm, I'm not sure. Currently we call forrest using: One way would be to ignore the exit code produced by this ant call, which is afaik not possible. Everything else, has to be done in the scripts provided by forrest :( So, it seems this is more a forrest issue. Perhaps adding a property that is evaluated by forrest? Carsten
Re: [site docs] build failing
David Crossley wrote: Upayavira wrote: David Crossley wrote: You do get that vital hint if there are *no* broken links. Huh? If you build a site that *has no* broken links, then you will get a successful build, and a reminder to check the broken links file. A reminder? I've never seen one. Is that provided by Forrest? If you build a site that *does have* broken links, then you will get a mention of the broken link as it goes past, and a "build failed" message at the end. However there is no message to check the broken links file. Fair enough. The details at the bottom of a site generation do not summarise the number of broken links. I'll add some kind of reporting of that to my todo list. Regards, Upayavira
Re: [site docs] build failing
Carsten Ziegeler wrote: Upayavira wrote: At the moment, if there are broken links, the CLI gives an error code. I could add a fail-on-broken="true/false" option. Would that do it? Ah, ok. Yes, I think the option is a very good idea! Thinking about it - can't you do that in Ant? Tell it whether to fail-on-error or not? If you can't I'll happily code it. Regards, Upayavira
RE: [site docs] build failing
Upayavira wrote: > > > At the moment, if there are broken links, the CLI gives an error code. I > could add a fail-on-broken="true/false" option. Would that do it? > Ah, ok. Yes, I think the option is a very good idea! Carsten
Re: [site docs] build failing
Upayavira wrote: > David Crossley wrote: > > >You do get that vital hint if there are *no* broken links. > > Huh? If you build a site that *has no* broken links, then you will get a successful build, and a reminder to check the broken links file. If you build a site that *does have* broken links, then you will get a mention of the broken link as it goes past, and a "build failed" message at the end. However there is no message to check the broken links file. > >Is that a Cocoon CLI bug or a Forrest bug? > > If I can understand what you're saying, maybe we can identify which. > > Regards, Upayavira
RE: [site docs] build failing
Carsten Ziegeler wrote: Upayavira wrote: David Crossley wrote: ... You do get that vital hint if there are *no* broken links. Huh? Is that a Cocoon CLI bug or a Forrest bug? If I can understand what you're saying, maybe we can identify which. There is definitly the bug that says "Build failed" at the end and the exit code 1 because this stops the ant task and the docs are not copied to the correct place. At the moment, if there are broken links, the CLI gives an error code. I could add a fail-on-broken="true/false" option. Would that do it? Regards, Upayavira
RE: [site docs] build failing
Upayavira wrote: > > David Crossley wrote: > > ... > > >You do get that vital hint if there are *no* broken links. > > > Huh? > > >Is that a Cocoon CLI bug or a Forrest bug? > > > > > If I can understand what you're saying, maybe we can identify which. > There is definitly the bug that says "Build failed" at the end and the exit code 1 because this stops the ant task and the docs are not copied to the correct place. Carsten
Re: [site docs] build failing
David Crossley wrote: ... You do get that vital hint if there are *no* broken links. Huh? Is that a Cocoon CLI bug or a Forrest bug? If I can understand what you're saying, maybe we can identify which. Regards, Upayavira
Re: [site docs] build failing
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 plan/changes.rss 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
[site docs] build failing
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, Tony
