Re: ForrestBot build for forrest-seed FAILED
Forrestbot wrote: [java] * [53/27] [2/34]0.4s 11.0Kb samples-b/embedded_html.html [java] ^samples-b/site:index [java] * [54/26] [0/2] 0.028s 3.6Kb samples-b/embedded_html.xml [java] * [55/25] [0/0] 0.214s 20.6Kb samples-b/embedded_html.pdf [java] java.util.ConcurrentModificationException: File /usr/home/forrest/htdocs/ft/build/forrest-seed/skin/basic.css is already being written by another thread [java] at org.apache.excalibur.source.impl.FileSource.getOutputStream(FileSource.java:333) [java] X [0] skin/basic.css BROKEN: URI not found: File /usr/home/forrest/htdocs/ft/build/forrest-seed/skin/basic.css is already being written by another thread [java] at org.apache.cocoon.bean.CocoonBean.processTarget(CocoonBean.java:549) [java] at org.apache.cocoon.bean.CocoonBean.process(CocoonBean.java:356) [java] at org.apache.cocoon.Main.main(Main.java:321) I removed the following file on the server. ~forrest/htdocs/ft/build/forrest-seed/skin/ -rw-rw-r-- 1 forrest forrest 0 Apr 19 02:14 basic.css.tmp No idea how it got there. All seems well now. -David
Re: ForrestBot build for forrest-seed FAILED
Automated build for forrest-seed FAILED init: [echo] Oops, something broke Oh that is an annoying message. I will ssh to the zone server and check the build system. -David
Re: ForrestBot build for forrest-seed FAILED
David Crossley wrote: Automated build for forrest-seed FAILED init: [echo] Oops, something broke Oh that is an annoying message. I will ssh to the zone server and check the build system. Ah, it is when the 'build clean; build of forrest has failed, then a subsequent cron job still tries to use that bad forrest. We need to enhance forrestbot to be smarter about that. Also need to enhance the setup on our zone. It is supposed to send us email when a forrest build itself fails. I turned all forrestbot jobs off on our zone. -David
Re: ForrestBot build for forrest-seed FAILED
I found why it is failing on our zone. Java 1.4 is in use there and its compile phase reports: /export/opt/forrest-trunk/main/java/org/apache/forrest/conf/AntPropertiesModule. java:31: cannot access org.apache.cocoon.components.modules.input.AbstractJXPath Module bad class file: /export/opt/forrest-trunk/lib/core/cocoon-2.1.12-dev.jar(org/apa che/cocoon/components/modules/input/AbstractJXPathModule.class) class file has wrong version 49.0, should be 48.0 So it seems that our new Cocoon jars were built with Java 1.5 Thorsten are you able to rebuild them. If no time now then say so and i will do it. -David
Re: ForrestBot build for forrest-seed FAILED
On Thu, 2008-09-11 at 17:08 +1000, David Crossley wrote: I found why it is failing on our zone. Java 1.4 is in use there and its compile phase reports: ... Thorsten are you able to rebuild them. If no time now then say so and i will do it. Doh, I am very sorry. Will do it now. salu2 -- Thorsten Scherler thorsten.at.apache.org Open Source Java consulting, training and solutions
Re: ForrestBot build for forrest-seed FAILED
On Thu, 2008-09-11 at 17:08 +1000, David Crossley wrote: Thorsten are you able to rebuild them. done now. salu2 -- Thorsten Scherler thorsten.at.apache.org Open Source Java consulting, training and solutions
Re: ForrestBot build for forrest-seed FAILED
Thorsten Scherler wrote: David Crossley wrote: Thorsten are you able to rebuild them. done now. Thanks. The rebuild of forrest on the zone just now completed sucessfully. I switched the forrestbot jobs back on. The first one will start 5 minutes after the hour mark. So we will see how we go on Solaris 10. -David
RE: ForrestBot build for forrest-seed FAILED
Well this seemed to pass my tests locally, its late I'll look in the morning and either fix it or revert. Gav... -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Sunday, 20 July 2008 12:04 AM To: Forrest developers Subject: ForrestBot build for forrest-seed FAILED Automated build for forrest-seed FAILED Log attached. -- Forrestbot run ended at 19 July 02:04 PM Using Forrest 0.9-dev Forrestbot administrator: Forrest developers -- [echo] ... Forrest render START 2008-07-19 02:04:08 ... Rendering docs in /export/home/config/forrestbot- trunk/conf/work/forrest-seed check-java-version: [echo] This is apache-forrest-0.9-dev [echo] Using Java 1.4 from /usr/j2se/jre init-props: [mkdir] Created dir: /export/home/config/forrestbot- trunk/conf/work/forrest-seed/tmp echo-settings: check-skin: init-proxy: fetch-skins-descriptors: fetch-skin: unpack-skins: init-skins: fetch-plugins-descriptors: [copy] Copying 1 file to /export/home/config/forrestbot- trunk/conf/work/forrest-seed/tmp [copy] Copying 1 file to /export/home/config/forrestbot- trunk/conf/work/forrest-seed/tmp [echo] Fetching plugins descriptor: http://forrest.apache.org/plugins/plugins.xml [get] Getting: http://forrest.apache.org/plugins/plugins.xml [get] To: /export/home/config/forrestbot-trunk/conf/work/forrest- seed/tmp/plugins-1.xml [get] local file date : Tue Apr 10 05:50:24 GMT+00:00 2007 [get] .. [get] last modified = Wed Apr 11 02:07:04 GMT+00:00 2007 [echo] Fetching plugins descriptor: http://forrest.apache.org/plugins/whiteboard-plugins.xml [get] Getting: http://forrest.apache.org/plugins/whiteboard- plugins.xml [get] To: /export/home/config/forrestbot-trunk/conf/work/forrest- seed/tmp/plugins-2.xml [get] local file date : Fri Feb 15 13:06:17 GMT+00:00 2008 [get] . [get] last modified = Sat Jul 19 10:07:27 GMT+00:00 2008 [echo] Plugin list loaded from http://forrest.apache.org/plugins/plugins.xml. [echo] Plugin list loaded from http://forrest.apache.org/plugins/whiteboard-plugins.xml. init-plugins: [mkdir] Created dir: /export/opt/forrest-trunk/build/plugins [mkdir] Created dir: /export/home/config/forrestbot- trunk/conf/work/forrest-seed/webapp/conf [copy] Copying 1 file to /export/home/config/forrestbot- trunk/conf/work/forrest-seed/tmp [copy] Copying 1 file to /export/home/config/forrestbot- trunk/conf/work/forrest-seed/tmp [copy] Copying 1 file to /export/home/config/forrestbot- trunk/conf/work/forrest-seed/tmp [copy] Copying 1 file to /export/home/config/forrestbot- trunk/conf/work/forrest-seed/tmp [copy] Copying 1 file to /export/home/config/forrestbot- trunk/conf/work/forrest-seed/tmp [echo] -- Installing plugin: org.apache.forrest.plugin.output.pdf -- check-plugin: [echo] org.apache.forrest.plugin.output.pdf is not available in the build dir. Trying to fetch it... init-props: echo-settings: init-proxy: fetch-plugins-descriptors: fetch-plugin: [echo] Trying to find the description of org.apache.forrest.plugin.output.pdf in the different descriptor files [echo] Using the descriptor file /export/home/config/forrestbot- trunk/conf/work/forrest-seed/tmp/plugins-1.xml... [xslt] Processing /export/home/config/forrestbot- trunk/conf/work/forrest-seed/tmp/plugins-1.xml to /export/home/config/forrestbot-trunk/conf/work/forrest- seed/tmp/pluginlist2fetchbuild.xml [xslt] Loading stylesheet /export/opt/forrest- trunk/main/var/pluginlist2fetch.xsl fetch-local-unversioned-plugin: get-local: [echo] Trying to locally get org.apache.forrest.plugin.output.pdf [echo] Looking in local /export/opt/forrest-trunk/plugins [echo] Found ! init-build-compiler: echo-init: init: compile: jar: local-deploy: [echo] Locally deploying org.apache.forrest.plugin.output.pdf [copy] Copying 28 files to /export/opt/forrest- trunk/build/plugins/org.apache.forrest.plugin.output.pdf [copy] Copying 1 file to /export/opt/forrest-trunk/build/plugins [copy] Copying 3 files to /export/opt/forrest-trunk/build/plugins/lib build: [echo] Plugin org.apache.forrest.plugin.output.pdf deployed ! Ready to configure fetch-remote-unversioned-plugin-version-forrest: fetch-remote-unversioned-plugin-unversion-forrest: has-been-downloaded: downloaded-message: uptodate-message: not-found-message: [echo] Fetch-plugin Ok, installing ! unpack-plugin: install-plugin: configure-plugin: configure-output-plugin: [echo] Mounting output plugin: org.apache.forrest.plugin.output.pdf
Re: ForrestBot build for forrest-seed FAILED
[EMAIL PROTECTED] wrote: Automated build for forrest-seed FAILED Log attached. -- Forrestbot run ended at 03 February 08:05 PM Using Forrest 0.9-dev Forrestbot administrator: Forrest developers [echo] Oops, something broke Just a reminder (as much to me as to everyone else)... Can we please do build test before committing changes. Thanks, Ross
Re: ForrestBot build for forrest-seed FAILED
Ross Gardler wrote: Gav wrote: So we can A) Revert as suggested. B) Add a full URI to a site.xml entry instead for the test sites. I like B better because it is a workaround to only the affected builds, and leaves others intact and using it properly. But that will still mean that the plugin docs will break and therefore we will not be able to deploy them. A is the only usable option to stop 50+ Forrestbot emails, we need to revert the change. I only have email access via webmail right now and it's really annoying and, I'm sure, will be annoying our lurkers. Especially when we already know the solution. Reverting the change fixes the problem with the forrestbot warnings, but doesn't not fix the real issue. However option B doesn't help either: there is still a management problem to remember to change the URL for the next release. The problem has only arisen really because we have included a 'Plugins' tab and a label to only the plugins index page, within the sample sites. Plugins are designed to be housed elsewhere, thus our plugins index page leads offsite. The idea of the plugins tab is to provide a way back to the forrest site. Any other solution would be fine, but any link back to Forrest would result in the same issue - site: does not work. Maybe another answer is to either 1. include all information on Plugins in the sample sites, meaning the usingPlugins and pluginInfrastructure pages are there too, providing a complete set of information. No, these are not sample sites they are documentation for the plugins. As documentation they are published on the website. We do not want to duplicate information, such as usingPlugins and pluginInfrastructure across 20+ plugin docs sites. I agree that we want to avoid duplication. Furthermore, I don't see how this would remove the link back to the core Forrest docs. Perhaps I am missing your point. I reckon that that link is the main issue. Tried to describe it at https://issues.apache.org/jira/browse/FOR-963 I am currently trying a new solution which passes a docs version parameter to the stylesheet so that the URL can be constructed. -David
Re: ForrestBot build for forrest-seed FAILED
Gav... wrote: ... I'll do as I'm told next time. :\ Heh - no. That's not how it works. Finding a proper fix is a better idea than a workaround, and having you look for one is great. The only point I was making, and I believe others were making, is that we need to think about the noise on the list. As David said, there is more than you as a committer. Ross
RE: ForrestBot build for forrest-seed FAILED
-Original Message- From: Thorsten Scherler [mailto:[EMAIL PROTECTED] Sent: Tuesday, 13 March 2007 10:57 AM To: dev@forrest.apache.org Subject: RE: ForrestBot build for forrest-seed FAILED On Mon, 2007-03-12 at 07:54 +0900, Gav wrote: -Original Message- From: Thorsten Scherler [mailto:[EMAIL PROTECTED] Sent: Monday, 12 March 2007 4:09 AM To: dev@forrest.apache.org Subject: RE: ForrestBot build for forrest-seed FAILED On Thu, 2007-03-08 at 21:34 +0900, Gav wrote: -Original Message- From: Ross Gardler [mailto:[EMAIL PROTECTED] Sent: Thursday, 8 March 2007 6:35 PM To: dev@forrest.apache.org Subject: Re: ForrestBot build for forrest-seed FAILED [EMAIL PROTECTED] wrote: Automated build for forrest-seed FAILED ... [java] X [0] pluginDocs/plugins_0_70/error:site:plugins/using BROKEN: No pipeline matched request: pluginDocs/plugins_0_70/error:site:plugins/using That was the reason for hard coded paths in the plugin docs. I think there is an issue somewhere about this. Ross Only thing I could find was https://issues.apache.org/jira/browse/FOR- 675 Seems to be it (also FOR-303) We have to fix this ASAP. The quick fix for now is to disable the cron job (AFAIR David is the owner) OR, which is preferable, to fix the linking! I guess the only thing that is missing is to add site:plugins/using to the site.xml. If nobody will do it, I will try to do it the next week but it would be nice if more people dig into thus things and fix it. We need more committer that can fix this, it cannot be always David and/or somebody else (normally Ross or me) that dig in (yes we all need time to understand and debug the things, but as more you do the faster you get). I will, if nobody beats me to it (which I honestly hope someone will), add site:plugins/using to the site.xml of both templates. In the site.xml of site-author we already have plugins label=0.80 Plugins href=pluginDocs/plugins_0_80/ tab=p0_80 index label=Index href=index.html/ using label=Using Plugins href=usingPlugins.html/ infrastructure label=Plugin Infrastructure href=pluginInfrastructure.html/ /plugins And plugins label=0.70 Plugins href=pluginDocs/plugins_0_70/ tab=p0_70 index label=Index href=index.html/ using label=Using Plugins href=usingPlugins.html/ infrastructure label=Plugin Infrastructure href=pluginInfrastructure.html/ /plugins So where else should I be looking? The zones example is based on the fresh site. There is neither a link nor a document for such linking in it. Ross provided http://svn.apache.org/viewvc/forrest/trunk/main/webapp/resources/styleshee ts/plugins-to-xdoc.xsl?r1=515849r2=515848pathrev=515849 The question that raises is ask by David commit message: Replace hard-coded URL to old usingPlugins doc with site: reference. Note: Was there a reason for this? The answer gives us the forrestbot by failing. I guess we should reverted like suggested by Ross. Ok , I've had another look now. We know the problem is due to the link not appearing in the site.xml file. Reverting the change will revert it for all webapp sites , yes? So we can A) Revert as suggested. B) Add a full URI to a site.xml entry instead for the test sites. I like B better because it is a workaround to only the affected builds, and leaves others intact and using it properly. The problem has only arisen really because we have included a 'Plugins' tab and a label to only the plugins index page, within the sample sites. Maybe another answer is to either 1. include all information on Plugins in the sample sites, meaning the usingPlugins and pluginInfrastructure pages are there too, providing a complete set of information. 2. Remove the Plugins Tab and Index entry from the sample sites. I don't mind either of these as another option to B. If someone wants to revert Davids change, fine go ahead, I don't like it, but I am only one voice :) If anyone likes any of my preferences, I will apply whichever one suits best. Gav... salu2 -- Thorsten Scherler thorsten.at.apache.org Open Source Java XMLconsulting, training and solutions
Re: ForrestBot build for forrest-seed FAILED
Gav wrote: -Original Message- From: Thorsten Scherler [mailto:[EMAIL PROTECTED] ... Ross provided http://svn.apache.org/viewvc/forrest/trunk/main/webapp/resources/styleshee ts/plugins-to-xdoc.xsl?r1=515849r2=515848pathrev=515849 The question that raises is ask by David commit message: Replace hard-coded URL to old usingPlugins doc with site: reference. Note: Was there a reason for this? The answer gives us the forrestbot by failing. I guess we should reverted like suggested by Ross. Ok , I've had another look now. We know the problem is due to the link not appearing in the site.xml file. Reverting the change will revert it for all webapp sites , yes? All *plugin* sites, yes. So we can A) Revert as suggested. B) Add a full URI to a site.xml entry instead for the test sites. I like B better because it is a workaround to only the affected builds, and leaves others intact and using it properly. But that will still mean that the plugin docs will break and therefore we will not be able to deploy them. A is the only usable option to stop 50+ Forrestbot emails, we need to revert the change. I only have email access via webmail right now and it's really annoying and, I'm sure, will be annoying our lurkers. Especially when we already know the solution. The problem has only arisen really because we have included a 'Plugins' tab and a label to only the plugins index page, within the sample sites. Plugins are designed to be housed elsewhere, thus our plugins index page leads offsite. The idea of the plugins tab is to provide a way back to the forrest site. Any other solution would be fine, but any link back to Forrest would result in the same issue - site: does not work. Maybe another answer is to either 1. include all information on Plugins in the sample sites, meaning the usingPlugins and pluginInfrastructure pages are there too, providing a complete set of information. No, these are not sample sites they are documentation for the plugins. As documentation they are published on the website. We do not want to duplicate information, such as usingPlugins and pluginInfrastructure across 20+ plugin docs sites. Furthermore, I don't see how this would remove the link back to the core Forrest docs. Perhaps I am missing your point. 2. Remove the Plugins Tab and Index entry from the sample sites. That is an option, as long as it means we have a dead end link that exists the Forrest site, possibly to some third party site. Personally, I prefer a simple workaround that works and does not create a dead end link. If anyone likes any of my preferences, I will apply whichever one suits best. Please, someone do something about these mails. We knew the problem within hours of the original commit. Get a workaround in place then decide the long term solution. I'm back on a proper connection tomorrow. I will revert the change straight away, that doesn't mean I won't welcome a better solution, it just means I don't think having these mails is helping us any in this situation. Ross
Re: ForrestBot build for forrest-seed FAILED
Ross Gardler wrote: Please, someone do something about these mails. We knew the problem within hours of the original commit. Get a workaround in place then decide the long term solution. I'm back on a proper connection tomorrow. I will revert the change straight away, that doesn't mean I won't welcome a better solution, it just means I don't think having these mails is helping us any in this situation. Youch, Sorry. I left on holidays soon after doing that change. Bit of a rush trying to get some things done to ease our release. Forgot to do 'build test'. No excuses. I am rather perplexed why no-one simply reverted my change. This is why there is more than one committer on a project. -David
Re: ForrestBot build for forrest-seed FAILED
quote who=David Crossley Ross Gardler wrote: Please, someone do something about these mails. We knew the problem within hours of the original commit. Get a workaround in place then decide the long term solution. I'm back on a proper connection tomorrow. I will revert the change straight away, that doesn't mean I won't welcome a better solution, it just means I don't think having these mails is helping us any in this situation. Youch, Sorry. I left on holidays soon after doing that change. Bit of a rush trying to get some things done to ease our release. Forgot to do 'build test'. No excuses. I am rather perplexed why no-one simply reverted my change. This is why there is more than one committer on a project. -David There was hints that the real solution should be found, so I started looking for one and came up with eventually, alternatives. Read the thread. Ross then wanted it reverting right away, he was not in a position to do so, I was, but carried on regardless looking for a better solution. I'll do as I'm told next time. :\ Gav... -- Gav...
Re: ForrestBot build for forrest-seed FAILED
Gav wrote: From: Ross Gardler That was the reason for hard coded paths in the plugin docs. I think there is an issue somewhere about this. Only thing I could find was https://issues.apache.org/jira/browse/FOR-675 Seems to be it (also FOR-303) No, they are not. The reason was as people later figured out: missing entry in the template site.xml to match site:plugins/using I couldn't find it so added: https://issues.apache.org/jira/browse/FOR-963 -David
RE: ForrestBot build for forrest-seed FAILED
-Original Message- From: Gav [mailto:[EMAIL PROTECTED] Sent: Monday, 12 March 2007 7:55 AM To: dev@forrest.apache.org Subject: RE: ForrestBot build for forrest-seed FAILED -Original Message- From: Thorsten Scherler [mailto:[EMAIL PROTECTED] Sent: Monday, 12 March 2007 4:09 AM To: dev@forrest.apache.org Subject: RE: ForrestBot build for forrest-seed FAILED On Thu, 2007-03-08 at 21:34 +0900, Gav wrote: -Original Message- From: Ross Gardler [mailto:[EMAIL PROTECTED] Sent: Thursday, 8 March 2007 6:35 PM To: dev@forrest.apache.org Subject: Re: ForrestBot build for forrest-seed FAILED [EMAIL PROTECTED] wrote: Automated build for forrest-seed FAILED ... [java] X [0] pluginDocs/plugins_0_70/error:site:plugins/usingBROKEN: No pipeline matched request: pluginDocs/plugins_0_70/error:site:plugins/using That was the reason for hard coded paths in the plugin docs. I think there is an issue somewhere about this. Ross Only thing I could find was https://issues.apache.org/jira/browse/FOR- 675 Seems to be it (also FOR-303) We have to fix this ASAP. The quick fix for now is to disable the cron job (AFAIR David is the owner) OR, which is preferable, to fix the linking! I guess the only thing that is missing is to add site:plugins/using to the site.xml. If nobody will do it, I will try to do it the next week but it would be nice if more people dig into thus things and fix it. We need more committer that can fix this, it cannot be always David and/or somebody else (normally Ross or me) that dig in (yes we all need time to understand and debug the things, but as more you do the faster you get). I will, if nobody beats me to it (which I honestly hope someone will), add site:plugins/using to the site.xml of both templates. In the site.xml of site-author we already have plugins label=0.80 Plugins href=pluginDocs/plugins_0_80/ tab=p0_80 index label=Index href=index.html/ using label=Using Plugins href=usingPlugins.html/ infrastructure label=Plugin Infrastructure href=pluginInfrastructure.html/ /plugins And plugins label=0.70 Plugins href=pluginDocs/plugins_0_70/ tab=p0_70 index label=Index href=index.html/ using label=Using Plugins href=usingPlugins.html/ infrastructure label=Plugin Infrastructure href=pluginInfrastructure.html/ /plugins So where else should I be looking? I have looked all over the place and still none the wiser as to why this is not working. Correct me if I'm wrong, site:plugins/using resolves to site == refer to site.xmap for internal URL converts to @src. plugins == refer to plugins section(s) and adds a href=pluginDocs/plugins_0_xx/ (xx being 70 or 80. /using == refer to using section of plugins section and adds href of usingPlugins.html. Now, I can see all over the place that site:plugins/index and site:plugins/infrastructure both work fine so sorry, don't know where else to look at this stage. I'd like to get it working but maybe need another hint. Gav... Thanks Gav...trying to understand :) salu2 -- Thorsten Scherler thorsten.at.apache.org Open Source Java XMLconsulting, training and solutions
RE: ForrestBot build for forrest-seed FAILED
On Mon, 2007-03-12 at 07:54 +0900, Gav wrote: -Original Message- From: Thorsten Scherler [mailto:[EMAIL PROTECTED] Sent: Monday, 12 March 2007 4:09 AM To: dev@forrest.apache.org Subject: RE: ForrestBot build for forrest-seed FAILED On Thu, 2007-03-08 at 21:34 +0900, Gav wrote: -Original Message- From: Ross Gardler [mailto:[EMAIL PROTECTED] Sent: Thursday, 8 March 2007 6:35 PM To: dev@forrest.apache.org Subject: Re: ForrestBot build for forrest-seed FAILED [EMAIL PROTECTED] wrote: Automated build for forrest-seed FAILED ... [java] X [0] pluginDocs/plugins_0_70/error:site:plugins/usingBROKEN: No pipeline matched request: pluginDocs/plugins_0_70/error:site:plugins/using That was the reason for hard coded paths in the plugin docs. I think there is an issue somewhere about this. Ross Only thing I could find was https://issues.apache.org/jira/browse/FOR- 675 Seems to be it (also FOR-303) We have to fix this ASAP. The quick fix for now is to disable the cron job (AFAIR David is the owner) OR, which is preferable, to fix the linking! I guess the only thing that is missing is to add site:plugins/using to the site.xml. If nobody will do it, I will try to do it the next week but it would be nice if more people dig into thus things and fix it. We need more committer that can fix this, it cannot be always David and/or somebody else (normally Ross or me) that dig in (yes we all need time to understand and debug the things, but as more you do the faster you get). I will, if nobody beats me to it (which I honestly hope someone will), add site:plugins/using to the site.xml of both templates. In the site.xml of site-author we already have plugins label=0.80 Plugins href=pluginDocs/plugins_0_80/ tab=p0_80 index label=Index href=index.html/ using label=Using Plugins href=usingPlugins.html/ infrastructure label=Plugin Infrastructure href=pluginInfrastructure.html/ /plugins And plugins label=0.70 Plugins href=pluginDocs/plugins_0_70/ tab=p0_70 index label=Index href=index.html/ using label=Using Plugins href=usingPlugins.html/ infrastructure label=Plugin Infrastructure href=pluginInfrastructure.html/ /plugins So where else should I be looking? The zones example is based on the fresh site. There is neither a link nor a document for such linking in it. Ross provided http://svn.apache.org/viewvc/forrest/trunk/main/webapp/resources/stylesheets/plugins-to-xdoc.xsl?r1=515849r2=515848pathrev=515849 The question that raises is ask by David commit message: Replace hard-coded URL to old usingPlugins doc with site: reference. Note: Was there a reason for this? The answer gives us the forrestbot by failing. I guess we should reverted like suggested by Ross. salu2 -- Thorsten Scherler thorsten.at.apache.org Open Source Java XMLconsulting, training and solutions
RE: ForrestBot build for forrest-seed FAILED
quote who=Thorsten Scherler On Mon, 2007-03-12 at 07:54 +0900, Gav wrote: -Original Message- From: Thorsten Scherler [mailto:[EMAIL PROTECTED] Sent: Monday, 12 March 2007 4:09 AM To: dev@forrest.apache.org Subject: RE: ForrestBot build for forrest-seed FAILED On Thu, 2007-03-08 at 21:34 +0900, Gav wrote: -Original Message- From: Ross Gardler [mailto:[EMAIL PROTECTED] Sent: Thursday, 8 March 2007 6:35 PM To: dev@forrest.apache.org Subject: Re: ForrestBot build for forrest-seed FAILED [EMAIL PROTECTED] wrote: Automated build for forrest-seed FAILED ... [java] X [0] pluginDocs/plugins_0_70/error:site:plugins/using BROKEN: No pipeline matched request: pluginDocs/plugins_0_70/error:site:plugins/using That was the reason for hard coded paths in the plugin docs. I think there is an issue somewhere about this. Ross Only thing I could find was https://issues.apache.org/jira/browse/FOR- 675 Seems to be it (also FOR-303) We have to fix this ASAP. The quick fix for now is to disable the cron job (AFAIR David is the owner) OR, which is preferable, to fix the linking! I guess the only thing that is missing is to add site:plugins/using to the site.xml. If nobody will do it, I will try to do it the next week but it would be nice if more people dig into thus things and fix it. We need more committer that can fix this, it cannot be always David and/or somebody else (normally Ross or me) that dig in (yes we all need time to understand and debug the things, but as more you do the faster you get). I will, if nobody beats me to it (which I honestly hope someone will), add site:plugins/using to the site.xml of both templates. In the site.xml of site-author we already have plugins label=0.80 Plugins href=pluginDocs/plugins_0_80/ tab=p0_80 index label=Index href=index.html/ using label=Using Plugins href=usingPlugins.html/ infrastructure label=Plugin Infrastructure href=pluginInfrastructure.html/ /plugins And plugins label=0.70 Plugins href=pluginDocs/plugins_0_70/ tab=p0_70 index label=Index href=index.html/ using label=Using Plugins href=usingPlugins.html/ infrastructure label=Plugin Infrastructure href=pluginInfrastructure.html/ /plugins So where else should I be looking? The zones example is based on the fresh site. There is neither a link nor a document for such linking in it. Ross provided http://svn.apache.org/viewvc/forrest/trunk/main/webapp/resources/stylesheets/plugins-to-xdoc.xsl?r1=515849r2=515848pathrev=515849 The question that raises is ask by David commit message: Replace hard-coded URL to old usingPlugins doc with site: reference. Note: Was there a reason for this? The answer gives us the forrestbot by failing. I guess we should reverted like suggested by Ross. Ok, so I'm a plonker for looking in the wrong place. I'll have another look when I get back later before commenting more. Gav... salu2 -- Thorsten Scherler thorsten.at.apache.org Open Source Java XMLconsulting, training and solutions -- Gav...
RE: ForrestBot build for forrest-seed FAILED
On Thu, 2007-03-08 at 21:34 +0900, Gav wrote: -Original Message- From: Ross Gardler [mailto:[EMAIL PROTECTED] Sent: Thursday, 8 March 2007 6:35 PM To: dev@forrest.apache.org Subject: Re: ForrestBot build for forrest-seed FAILED [EMAIL PROTECTED] wrote: Automated build for forrest-seed FAILED ... [java] X [0] pluginDocs/plugins_0_70/error:site:plugins/usingBROKEN: No pipeline matched request: pluginDocs/plugins_0_70/error:site:plugins/using That was the reason for hard coded paths in the plugin docs. I think there is an issue somewhere about this. Ross Only thing I could find was https://issues.apache.org/jira/browse/FOR-675 Seems to be it (also FOR-303) We have to fix this ASAP. The quick fix for now is to disable the cron job (AFAIR David is the owner) OR, which is preferable, to fix the linking! I guess the only thing that is missing is to add site:plugins/using to the site.xml. If nobody will do it, I will try to do it the next week but it would be nice if more people dig into thus things and fix it. We need more committer that can fix this, it cannot be always David and/or somebody else (normally Ross or me) that dig in (yes we all need time to understand and debug the things, but as more you do the faster you get). I will, if nobody beats me to it (which I honestly hope someone will), add site:plugins/using to the site.xml of both templates. salu2 -- Thorsten Scherler thorsten.at.apache.org Open Source Java XMLconsulting, training and solutions
RE: ForrestBot build for forrest-seed FAILED
-Original Message- From: Thorsten Scherler [mailto:[EMAIL PROTECTED] Sent: Monday, 12 March 2007 4:09 AM To: dev@forrest.apache.org Subject: RE: ForrestBot build for forrest-seed FAILED On Thu, 2007-03-08 at 21:34 +0900, Gav wrote: -Original Message- From: Ross Gardler [mailto:[EMAIL PROTECTED] Sent: Thursday, 8 March 2007 6:35 PM To: dev@forrest.apache.org Subject: Re: ForrestBot build for forrest-seed FAILED [EMAIL PROTECTED] wrote: Automated build for forrest-seed FAILED ... [java] X [0] pluginDocs/plugins_0_70/error:site:plugins/using BROKEN: No pipeline matched request: pluginDocs/plugins_0_70/error:site:plugins/using That was the reason for hard coded paths in the plugin docs. I think there is an issue somewhere about this. Ross Only thing I could find was https://issues.apache.org/jira/browse/FOR- 675 Seems to be it (also FOR-303) We have to fix this ASAP. The quick fix for now is to disable the cron job (AFAIR David is the owner) OR, which is preferable, to fix the linking! I guess the only thing that is missing is to add site:plugins/using to the site.xml. If nobody will do it, I will try to do it the next week but it would be nice if more people dig into thus things and fix it. We need more committer that can fix this, it cannot be always David and/or somebody else (normally Ross or me) that dig in (yes we all need time to understand and debug the things, but as more you do the faster you get). I will, if nobody beats me to it (which I honestly hope someone will), add site:plugins/using to the site.xml of both templates. In the site.xml of site-author we already have plugins label=0.80 Plugins href=pluginDocs/plugins_0_80/ tab=p0_80 index label=Index href=index.html/ using label=Using Plugins href=usingPlugins.html/ infrastructure label=Plugin Infrastructure href=pluginInfrastructure.html/ /plugins And plugins label=0.70 Plugins href=pluginDocs/plugins_0_70/ tab=p0_70 index label=Index href=index.html/ using label=Using Plugins href=usingPlugins.html/ infrastructure label=Plugin Infrastructure href=pluginInfrastructure.html/ /plugins So where else should I be looking? Thanks Gav...trying to understand :) salu2 -- Thorsten Scherler thorsten.at.apache.org Open Source Java XMLconsulting, training and solutions
Re: ForrestBot build for forrest-seed FAILED
Do we want to revert http://svn.apache.org/viewvc/forrest/trunk/main/webapp/resources/stylesheets/plugins-to-xdoc.xsl?r1=515849r2=515848pathrev=515849 At least it will stop forrestbot getting carried away us (I'm away for a few days, so it's up to someone else). Ross
Re: ForrestBot build for forrest-seed FAILED
[EMAIL PROTECTED] wrote: Automated build for forrest-seed FAILED ... [java] X [0] pluginDocs/plugins_0_70/error:site:plugins/using BROKEN: No pipeline matched request: pluginDocs/plugins_0_70/error:site:plugins/using That was the reason for hard coded paths in the plugin docs. I think there is an issue somewhere about this. Ross
RE: ForrestBot build for forrest-seed FAILED
-Original Message- From: Ross Gardler [mailto:[EMAIL PROTECTED] Sent: Thursday, 8 March 2007 6:35 PM To: dev@forrest.apache.org Subject: Re: ForrestBot build for forrest-seed FAILED [EMAIL PROTECTED] wrote: Automated build for forrest-seed FAILED ... [java] X [0] pluginDocs/plugins_0_70/error:site:plugins/using BROKEN: No pipeline matched request: pluginDocs/plugins_0_70/error:site:plugins/using That was the reason for hard coded paths in the plugin docs. I think there is an issue somewhere about this. Ross Only thing I could find was https://issues.apache.org/jira/browse/FOR-675 Seems to be it (also FOR-303) Gav...
Re: ForrestBot build for forrest-seed FAILED
On Tue, 2007-01-30 at 12:56 +, [EMAIL PROTECTED] wrote: ... configure-plugin-locationmap: [echo] Mounting plugin locationmap for org.apache.forrest.plugin.output.pdf [xslt] Processing /export/home/config/forrestbot-trunk/conf/work/forrest-seed/tmp/locationmap.xml to /export/home/config/forrestbot-trunk/conf/work/forrest-seed/tmp/locationmap.xml.new [xslt] Loading stylesheet /export/opt/forrest-trunk/main/var/pluginLmMountSnippet.xsl [move] Moving 1 file to /export/home/config/forrestbot-trunk/conf/work/forrest-seed/tmp init: [echo] Oops, something broke Somebody knows what is going on. Normally this error mail is related with network problems, but not sure anymore. somebody has an idea? salu2
Re: ForrestBot build for forrest-seed FAILED
[EMAIL PROTECTED] wrote: Automated build for forrest-seed FAILED Log attached. This has happened a few times. But I do not see a problem locally. Can it be that the cron job to update Forrest from SVN is overlapping with the building of Forrest Seed (reminder for David, remember the Cocoon overlap that caused similar effects). Ross
Re: ForrestBot build for forrest-seed FAILED
[EMAIL PROTECTED] wrote: Automated build for forrest-seed FAILED Log attached. ... WARNING === Unable to load plugin list number 1 from http://forrest.apache.org/plugins/plugins.xml. Any plugins identified in this plugin list cannot be installed automatially, see further errors below. Should be a temporary server glitch. Lets see if the build starts working again. This kind of problem will go away when we can dynamically generate the plugins.xml file from the plugin build files and we marry this to the automatic local deployment. Ross
Re: ForrestBot build for forrest-seed FAILED
[EMAIL PROTECTED] wrote: Automated build for forrest-seed FAILED Log attached. Is there something missing in these logs? I can't see what the failure is (complete log below). Ross -- Forrestbot run ended at 09 December 02:55 PM Using Forrest 0.8-dev Forrestbot administrator: Forrest developers -- [echo] ... Forrest render START 2005-12-09 02:55:07 ... Rendering docs in /export/home/config/forrestbot-trunk/conf/work/forrest-seed check-java-version: [echo] This is apache-forrest-0.8-dev [echo] Using Java 1.4 from /usr/j2se/jre init-props: [mkdir] Created dir: /export/home/config/forrestbot-trunk/conf/work/forrest-seed/tmp echo-settings: check-skin: init-proxy: fetch-skins-descriptors: fetch-skin: unpack-skins: init-skins: init-plugins: [mkdir] Created dir: /export/home/config/forrestbot-trunk/conf/work/forrest-seed/webapp/conf [copy] Copying 1 file to /export/home/config/forrestbot-trunk/conf/work/forrest-seed/tmp [copy] Copying 1 file to /export/home/config/forrestbot-trunk/conf/work/forrest-seed/tmp [copy] Copying 1 file to /export/home/config/forrestbot-trunk/conf/work/forrest-seed/tmp [copy] Copying 1 file to /export/home/config/forrestbot-trunk/conf/work/forrest-seed/tmp [copy] Copying 1 file to /export/home/config/forrestbot-trunk/conf/work/forrest-seed/tmp [echo] Installing plugin: org.apache.forrest.plugin.output.pdf check-plugin: [echo] org.apache.forrest.plugin.output.pdf is not available in the build dir init-props: echo-settings: init-proxy: fetch-plugins-descriptors: [echo] Fetching plugins descriptor: http://forrest.apache.org/plugins/plugins.xml [get] Getting: http://forrest.apache.org/plugins/plugins.xml [get] . [get] last modified = Thu Nov 24 11:07:14 GMT+00:00 2005 [echo] Fetching plugins descriptor: http://forrest.apache.org/plugins/whiteboard-plugins.xml [get] Getting: http://forrest.apache.org/plugins/whiteboard-plugins.xml [get] .. [get] last modified = Sun Nov 27 03:07:04 GMT+00:00 2005 [echo] Plugin list loaded from http://forrest.apache.org/plugins/plugins.xml. [echo] Plugin list loaded from http://forrest.apache.org/plugins/whiteboard-plugins.xml. fetch-plugin: [xslt] Processing /export/home/config/forrestbot-trunk/conf/work/forrest-seed/tmp/plugins-1.xml to /export/home/config/forrestbot-trunk/conf/work/forrest-seed/tmp/pluginlist2fetchbuild.xml [xslt] Loading stylesheet /export/opt/forrest-trunk/main/var/pluginlist2fetch.xsl fetch-versioned-plugin: fetch-unversioned-plugin: [echo] Versioned plugin unavailable, trying to get versionless plugin... [get] Getting: http://forrest.apache.org/plugins//org.apache.forrest.plugin.output.pdf.zip [get] . [get] last modified = Fri Jul 08 16:07:18 GMT+00:00 2005 final-check: [echo] org.apache.forrest.plugin.output.pdf downloaded, ready to install fetchplugin: [xslt] Processing /export/home/config/forrestbot-trunk/conf/work/forrest-seed/tmp/plugins-2.xml to /export/home/config/forrestbot-trunk/conf/work/forrest-seed/tmp/pluginlist2fetchbuild.xml [xslt] Loading stylesheet /export/opt/forrest-trunk/main/var/pluginlist2fetch.xsl findPlugin: unpack-plugin: extract-plugin: [unzip] Expanding: /export/opt/forrest-trunk/build/plugins/org.apache.forrest.plugin.output.pdf.zip into /export/opt/forrest-trunk/build/plugins/org.apache.forrest.plugin.output.pdf [delete] Deleting 1 files from /export/opt/forrest-trunk/build/plugins install-plugin: configure-plugin: configure-output-plugin: [echo] Mounting output plugin: org.apache.forrest.plugin.output.pdf [xslt] Processing /export/home/config/forrestbot-trunk/conf/work/forrest-seed/tmp/output.xmap to /export/home/config/forrestbot-trunk/conf/work/forrest-seed/tmp/output.xmap.new [xslt] Loading stylesheet /export/opt/forrest-trunk/main/var/pluginMountSnippet.xsl [move] Moving 1 files to /export/home/config/forrestbot-trunk/conf/work/forrest-seed/tmp configure-plugin-locationmap: [echo] Mounting plugin locationmap for org.apache.forrest.plugin.output.pdf [xslt] Processing /export/home/config/forrestbot-trunk/conf/work/forrest-seed/tmp/locationmap.xml to /export/home/config/forrestbot-trunk/conf/work/forrest-seed/tmp/locationmap.xml.new [xslt] Loading stylesheet /export/opt/forrest-trunk/main/var/pluginLmMountSnippet.xsl [move] Moving 1 files to /export/home/config/forrestbot-trunk/conf/work/forrest-seed/tmp init: [echo] Oops, something broke
Re: ForrestBot build for forrest-seed FAILED
[EMAIL PROTECTED] wrote: Automated build for forrest-seed FAILED Can anyone see the problem with this. I realise it is a temporary, network related problem and that usually the forrestbot builds with no problems. But I can't see what has caused the 4 or 5 failures we've had in the last couple of days. Ross
Re: ForrestBot build for forrest-seed FAILED
On Sunday 09 October 2005 9:55 pm, [EMAIL PROTECTED] wrote: Automated build for forrest-seed FAILED Hey everyone, I think the renaming of files broke something. I'm on it, just hang in there (or don't update just yet). Sorry abt that, Diwaker -- Web/Blog/Gallery: http://floatingsun.net On Apache: http://people.apache.org/~diwaker
Re: ForrestBot build for forrest-seed FAILED
[EMAIL PROTECTED] wrote: Automated build for forrest-seed FAILED I am sure that if was the upgrade of the libraries (Avalon, Excalibur) what caused that.. There was an ok build at forrest-seed-20050918095503.log I can revert that, but it makes harder to see the problem in order to resolved. WDYT? Cheers, cheche
Re: ForrestBot build for forrest-seed FAILED
Automated build for forrest-seed FAILED [snip] [java] * [37/25] [2/32]0.803s 10.9Kb samples/locationmap/index.html [java] * [38/24] [0/0] 0.44s 8.7Kb samples/locationmap/index.pdf [java] X [0] samples/locationmap/lm:rewriteDemo/indexBROKEN: No pipeline matched request: samples/locationmap/lm:rewriteDemo/index ... Everything was okay at r289911 which was just before the upgrade of the many other jars in lib/core at r289912. So the upgrade of the Cocoon jars before that was okay. I suppose the best way is to roll back each of those jars until we find the culprit. -David
Re: ForrestBot build for forrest-seed FAILED
Juan Jose Pablos wrote: [EMAIL PROTECTED] wrote: Automated build for forrest-seed FAILED I am sure that if was the upgrade of the libraries (Avalon, Excalibur) what caused that.. There was an ok build at forrest-seed-20050918095503.log I can revert that, but it makes harder to see the problem in order to resolved. WDYT? My view is we should find the root cause of the problem and, if necessary, fix in Cocoon. Having said that 'i don't have any time to help, so whatever you have the time for is fine by me. Ross
Re: ForrestBot build for forrest-seed FAILED
David Crossley wrote: Automated build for forrest-seed FAILED [snip] [java] * [37/25] [2/32]0.803s 10.9Kb samples/locationmap/index.html [java] * [38/24] [0/0] 0.44s 8.7Kb samples/locationmap/index.pdf [java] X [0] samples/locationmap/lm:rewriteDemo/index BROKEN: No pipeline matched request: samples/locationmap/lm:rewriteDemo/index ... Everything was okay at r289911 which was just before the upgrade of the many other jars in lib/core at r289912. So the upgrade of the Cocoon jars before that was okay. I suppose the best way is to roll back each of those jars until we find the culprit. The cause was the upgrade of excalibur-sourceresolve. Why i don't know. Reverted from excalibur-sourceresolve-2.1.jar to excalibur-sourceresolve-1.1.jar at r289917 which fixed it. As Ross said we need to find the real reason. -David
