Re: [Vote] Cocoon Release 2.1.11
On Jan 3, 2008 6:16 AM, David Crossley [EMAIL PROTECTED] wrote: ...I used the tar.gz and verified the md5sum and pgp signature, and investigated some other things. md5: f103d7c90fcd1e0f027f88f7fd0a44a0... Automated tests (both junit-tests and htmlunit-tests) work for me on macosx / JDK 1.5, using this same distribution archive. +1 for the release, thanks everybody for your work! -Bertrand
Re: [Vote] Cocoon Release 2.1.11
Carsten Ziegeler pisze: As this is currently the quiet season of the year, I'll leave the vote open until monday. Could you leave it open until today's night? I'll definitely want to have a look at it. -- Grzegorz Kossakowski Committer and PMC Member of Apache Cocoon http://reflectingonthevicissitudes.wordpress.com/
Re: [Vote] Cocoon Release 2.1.11
Carsten Ziegeler wrote: Hi, i've put up the 2.1.11 release at: http://people.apache.org/~cziegeler/releases/cocoon/ I'm just looking through JIRA and note that the version still uses an antiquated version of ehcache. By that I mean, a version that does not do large distributed caching properly. Large caches must be recreated on server restart and fall over when distributed caching is attempted. Simply replacing the ehcache.jar is not a clean solution as ehcache will write all its files to java.io.tmpdir and produce many warnings whenever used. This is an open issue for C2.2, so I feel it would be something that needs to be looked at before a final release. DISCLAIMER: I'm still finding my way around the cocoon codebase and may be missing something obvious to the old hands. :-) Regards, Alec.
Re: [Vote] Cocoon Release 2.1.11
Grzegorz Kossakowski wrote: Carsten Ziegeler pisze: As this is currently the quiet season of the year, I'll leave the vote open until monday. Could you leave it open until today's night? I'll definitely want to have a look at it. No problem, I'll close the vote tomorrow. Carsten -- Carsten Ziegeler [EMAIL PROTECTED]
Test, please ignore
Sorry for the noise, I'm having problems sending messages to Apache mailing lists. Ugo
Re: [Vote] Cocoon Release 2.1.11
Hi Alec, This is a great improvement! However, we cannot use a newer ehcache version, cuz we must keep cocoon 2.1.x branch compatible with java 1.3. :S Currently, we use ehcache 1.2.3. The 1.2.4 did drop support for java 1.3 [1] Best Regards, Antonio Gallardo. [1] http://ehcache.sourceforge.net/changes-report.html#1.2.4RC Alec Bickerton escribió: Carsten Ziegeler wrote: Hi, i've put up the 2.1.11 release at: http://people.apache.org/~cziegeler/releases/cocoon/ I'm just looking through JIRA and note that the version still uses an antiquated version of ehcache. By that I mean, a version that does not do large distributed caching properly. Large caches must be recreated on server restart and fall over when distributed caching is attempted. Simply replacing the ehcache.jar is not a clean solution as ehcache will write all its files to java.io.tmpdir and produce many warnings whenever used. This is an open issue for C2.2, so I feel it would be something that needs to be looked at before a final release. DISCLAIMER: I'm still finding my way around the cocoon codebase and may be missing something obvious to the old hands. :-) Regards, Alec.
Re: [Vote] Cocoon Release 2.1.11
I was not able to test it with the CMS today, but on both my Ubuntu laptop with JDK 1.5 and on my desktop WinXP JDK 1.4 all seems fine! +1 Jeroen On Mon, 2008-01-07 at 09:27 -0600, Antonio Gallardo wrote: Hi Alec, This is a great improvement! However, we cannot use a newer ehcache version, cuz we must keep cocoon 2.1.x branch compatible with java 1.3. :S Currently, we use ehcache 1.2.3. The 1.2.4 did drop support for java 1.3 [1] Best Regards, Antonio Gallardo. [1] http://ehcache.sourceforge.net/changes-report.html#1.2.4RC Alec Bickerton escribió: Carsten Ziegeler wrote: Hi, i've put up the 2.1.11 release at: http://people.apache.org/~cziegeler/releases/cocoon/ I'm just looking through JIRA and note that the version still uses an antiquated version of ehcache. By that I mean, a version that does not do large distributed caching properly. Large caches must be recreated on server restart and fall over when distributed caching is attempted. Simply replacing the ehcache.jar is not a clean solution as ehcache will write all its files to java.io.tmpdir and produce many warnings whenever used. This is an open issue for C2.2, so I feel it would be something that needs to be looked at before a final release. DISCLAIMER: I'm still finding my way around the cocoon codebase and may be missing something obvious to the old hands. :-) Regards, Alec.
Re: broken 2.1 docs - something changed in Daisy?
I found the problem. The connection between Forrest and Daisy on the ASF Zones server is very slow. The Cocoon-2.1 docs job takes so long to complete, that it gets clobbered by another cron job. It seems to be a network issue that Forrest developers should report to ASF Infrastructure. First we should make double-sure that it is not a problem with our Forrest-Daisy plugin. You can see how slow it is by the doc generation times in the forrestbot report below. The job runs at 0:04 and 12:04 daily, so to see it running: ssh forrest.zones.apache.org tail -f $CONFIG/forrestbot-trunk/logs/cocoon-docs.log http://forrest.apache.org/zone.html -David David Crossley wrote: See http://forrest.zones.apache.org/ In the Cocoon 2.1 Docs follow the brokenlinks doc. Something about Daisy document ID 655, whatever that is. By the way, other Cocoon docs sections are old and we need to remove them from our Forrest zone. -David On Thu, Jan 03, 2008 at 01:05:52PM +, [EMAIL PROTECTED] wrote: Automated build for cocoon-docs FAILED Log attached. -- Forrestbot run ended at 03 January 01:05 PM Using Forrest 0.9-dev Forrestbot administrator: ForrestBot -- [echo] ... Forrest render START 2008-01-03 12:22:32 ... Rendering docs in /export/home/config/forrestbot-trunk/conf/work/cocoon-docs 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/cocoon-docs/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/cocoon-docs/tmp [copy] Copying 1 file to /export/home/config/forrestbot-trunk/conf/work/cocoon-docs/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/cocoon-docs/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/cocoon-docs/tmp/plugins-2.xml [get] local file date : Sat Sep 01 21:45:45 GMT+00:00 2007 [get] Not modified - so not downloaded [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/home/config/forrestbot-trunk/conf/work/cocoon-docs/webapp/conf [copy] Copying 1 file to /export/home/config/forrestbot-trunk/conf/work/cocoon-docs/tmp [copy] Copying 1 file to /export/home/config/forrestbot-trunk/conf/work/cocoon-docs/tmp [copy] Copying 1 file to /export/home/config/forrestbot-trunk/conf/work/cocoon-docs/tmp [copy] Copying 1 file to /export/home/config/forrestbot-trunk/conf/work/cocoon-docs/tmp [copy] Copying 1 file to /export/home/config/forrestbot-trunk/conf/work/cocoon-docs/tmp [echo] -- Installing plugin: org.apache.forrest.plugin.output.pdf -- check-plugin: [echo] org.apache.forrest.plugin.output.pdf is available in the build dir. Trying to update 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/cocoon-docs/tmp/plugins-1.xml... [xslt] Processing /export/home/config/forrestbot-trunk/conf/work/cocoon-docs/tmp/plugins-1.xml to /export/home/config/forrestbot-trunk/conf/work/cocoon-docs/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 build: [echo] Plugin
Re: [Vote] Cocoon Release 2.1.11
David Crossley wrote: Would someone please look at why a recent change in Daisy seemed to break the automated building of 2.1 docs. I am away now for our weekend. http://article.gmane.org/gmane.text.xml.cocoon.devel/76511 Perhaps browse the docs@ list in the period prior to the first forrestbot report. I found the problem. The connection between Forrest and Daisy on the ASF Zones server is very slow. The Cocoon-2.1 docs job takes so long to complete, that it gets clobbered by another cron job. See the above link for more info. -David
Re: svn commit: r609282 [1/2] - in /cocoon/trunk: blocks/cocoon-core-sample/cocoon-core-main-sample/src/main/resources/COB-INF/modules/ blocks/cocoon-core-sample/cocoon-core-main-sample/src/main/resou
Ralph Goers wrote: I didn't know about the plugin, but yes I knew I should have put the issue number in the commit. I just forgot to do it. Do: svn propedit svn:log --revprop -r609282 https://svn.apache.org/repos/asf/cocoon/trunk -David Joerg Heinicke wrote: On 06.01.2008 04:35, [EMAIL PROTECTED] wrote: Author: rgoers Date: Sun Jan 6 01:35:48 2008 New Revision: 609282 URL: http://svn.apache.org/viewvc?rev=609282view=rev Log: Created XPathXMLFileModule to fix problems with XMLFileModule. Added getAttributeValue to JXPathHelper and changed all references to getAttribute to use it instead. Moved registration of VariableResolver to BridgeElementParser from SitemapElementParser to make it available to all Avalon components (i.e. input modules). Hi Ralph, I don't know if it just slipped through in this commit: If you add the issue number to the commit message, the SVN plugin for Jira can link the revision to the issue and adds nice links as it happened for your commit to 2.1 branch: https://issues.apache.org/jira/browse/COCOON-1574?page=com.atlassian.jira.plugin.ext.subversion:subversion-commits-tabpanel Joerg
Re: broken 2.1 docs - something changed in Daisy?
Argh, forgot to Cc forrest dev. -David David Crossley wrote: I found the problem. The connection between Forrest and Daisy on the ASF Zones server is very slow. The Cocoon-2.1 docs job takes so long to complete, that it gets clobbered by another cron job. It seems to be a network issue that Forrest developers should report to ASF Infrastructure. First we should make double-sure that it is not a problem with our Forrest-Daisy plugin. You can see how slow it is by the doc generation times in the forrestbot report below. The job runs at 0:04 and 12:04 daily, so to see it running: ssh forrest.zones.apache.org tail -f $CONFIG/forrestbot-trunk/logs/cocoon-docs.log http://forrest.apache.org/zone.html -David David Crossley wrote: See http://forrest.zones.apache.org/ In the Cocoon 2.1 Docs follow the brokenlinks doc. Something about Daisy document ID 655, whatever that is. By the way, other Cocoon docs sections are old and we need to remove them from our Forrest zone. -David On Thu, Jan 03, 2008 at 01:05:52PM +, [EMAIL PROTECTED] wrote: Automated build for cocoon-docs FAILED Log attached. -- Forrestbot run ended at 03 January 01:05 PM Using Forrest 0.9-dev Forrestbot administrator: ForrestBot -- [echo] ... Forrest render START 2008-01-03 12:22:32 ... Rendering docs in /export/home/config/forrestbot-trunk/conf/work/cocoon-docs 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/cocoon-docs/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/cocoon-docs/tmp [copy] Copying 1 file to /export/home/config/forrestbot-trunk/conf/work/cocoon-docs/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/cocoon-docs/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/cocoon-docs/tmp/plugins-2.xml [get] local file date : Sat Sep 01 21:45:45 GMT+00:00 2007 [get] Not modified - so not downloaded [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/home/config/forrestbot-trunk/conf/work/cocoon-docs/webapp/conf [copy] Copying 1 file to /export/home/config/forrestbot-trunk/conf/work/cocoon-docs/tmp [copy] Copying 1 file to /export/home/config/forrestbot-trunk/conf/work/cocoon-docs/tmp [copy] Copying 1 file to /export/home/config/forrestbot-trunk/conf/work/cocoon-docs/tmp [copy] Copying 1 file to /export/home/config/forrestbot-trunk/conf/work/cocoon-docs/tmp [copy] Copying 1 file to /export/home/config/forrestbot-trunk/conf/work/cocoon-docs/tmp [echo] -- Installing plugin: org.apache.forrest.plugin.output.pdf -- check-plugin: [echo] org.apache.forrest.plugin.output.pdf is available in the build dir. Trying to update 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/cocoon-docs/tmp/plugins-1.xml... [xslt] Processing /export/home/config/forrestbot-trunk/conf/work/cocoon-docs/tmp/plugins-1.xml to /export/home/config/forrestbot-trunk/conf/work/cocoon-docs/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]
Re: Question about sample site in trunk
On Jan 7, 2008, at 2:32 AM, Ralph Goers wrote: But if they want to build the sample site and run it what would they do? Create pom.xml inheriting from core/cocoon-webapp and add dependencies to all of the *-sample blocks you want, followed by mvn install jetty:run should do it. Vadim
Re: Question about sample site in trunk
How hard would it be to create an archetype to create the pom automatically? Users would then either just build and run it or edit it first to remove stuff they don't care about. Telling them to create pom.xml inheriting from core-cocoon-webapp still requires that they a) know how to do that and b) know what samples exist that they can add. Ralph Vadim Gritsenko wrote: On Jan 7, 2008, at 2:32 AM, Ralph Goers wrote: But if they want to build the sample site and run it what would they do? Create pom.xml inheriting from core/cocoon-webapp and add dependencies to all of the *-sample blocks you want, followed by mvn install jetty:run should do it. Vadim
