http://blog.gmane.org/gmane.text.xml.forrest.devel hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://permalink.gmane.org/gmane.text.xml.forrest.devel/28740 <pre> [ https://issues.apache.org/jira/browse/FOR-1193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&amp;focusedCommentId=13593496#comment-13593496 ] David Crossley commented on FOR-1193: ------------------------------------- Our special stuff is not needed anymore. The Cocoon FOP Block has been upgraded to use FOP-1.0 (See COCOON-2295). So far only done in our "update_cocoon_2.1.12" branch. We should also be able to upgrade to FOP-1.1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira </pre> David Crossley (JIRA 2013-03-05T15:45:20 http://permalink.gmane.org/gmane.text.xml.forrest.devel/28739 <pre> [ https://issues.apache.org/jira/browse/FOR-1240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&amp;focusedCommentId=13593466#comment-13593466 ] David Crossley commented on FOR-1240: ------------------------------------- https://svn.apache.org/repos/asf/forrest/branches/update_cocoon_2.1.12 Following $FORREST_HOME/etc/cocoon_upgrade/ Not yet done Step 8 or Step 9. The branch is ready now for people to do further improvements and bug fixing. When the Cocoon release happens then we can follow the upgrade process again. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira </pre> David Crossley (JIRA 2013-03-05T15:19:13 http://permalink.gmane.org/gmane.text.xml.forrest.devel/28738 <pre> [ https://issues.apache.org/jira/browse/FOR-1241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Crossley updated FOR-1241: -------------------------------- Attachment: error.txt Attached is "error.txt" being the trace from one of the corner images. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira </pre> David Crossley (JIRA 2013-03-05T15:15:13 http://permalink.gmane.org/gmane.text.xml.forrest.devel/28737 <pre>David Crossley created FOR-1241: ----------------------------------- Summary: round corner PNGs are not being generated in the "update_cocoon_2.1.12" branch Key: FOR-1241 URL: https://issues.apache.org/jira/browse/FOR-1241 Project: Forrest Issue Type: Bug Components: Skins (general issues) Affects Versions: 0.10-dev Reporter: David Crossley Fix For: 0.10-dev The generation of the round corner PNGs is not happening in the "update_cocoon_2.1.12" branch: "java.lang.ClassCastException: org.apache.batik.dom.GenericElement" -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira </pre> David Crossley (JIRA 2013-03-05T15:11:15 http://permalink.gmane.org/gmane.text.xml.forrest.devel/28736 <pre> [ https://issues.apache.org/jira/browse/FOR-1240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&amp;focusedCommentId=13593212#comment-13593212 ] David Crossley commented on FOR-1240: ------------------------------------- I upgraded my Forrest to use current Cocoon-2.1.12-dev and it seems okay (see the abovementioned thread). This also had upgraded FOP, Batik, etc. Going to make a branch in Forrest SVN to do this upgrade, then follow on after the Cocoon release. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira </pre> David Crossley (JIRA 2013-03-05T08:08:11 http://permalink.gmane.org/gmane.text.xml.forrest.devel/28735 <pre> I added this today: https://issues.apache.org/jira/browse/COCOON-2335 Then closed it again, because all is okay using Java 1.4.2 which is the version for Cocoon-2.1.12+ The text is missing when using Java 5. -David </pre> David Crossley 2013-03-04T06:51:38 http://permalink.gmane.org/gmane.text.xml.forrest.devel/28734 <pre> [ https://issues.apache.org/jira/browse/FOR-915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&amp;focusedCommentId=13562606#comment-13562606 ] Kristian Waagan commented on FOR-915: ------------------------------------- Apache Derby is having this problem for its site, but we've learned to work around it by simply reverting the changed PNGs after site generation. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira </pre> Kristian Waagan (JIRA 2013-01-25T11:13:12 http://permalink.gmane.org/gmane.text.xml.forrest.devel/28733 <pre>Den 24. jan 2013 kl. 22:33 skrev Tim Williams: Agrre, I'll commit. :) Sjur </pre> Sjur Moshagen 2013-01-24T21:35:46 http://permalink.gmane.org/gmane.text.xml.forrest.devel/28732 <pre> Ooops.. dangling pronoun:( "we" == forrest.apache.org :) --tim </pre> Tim Williams 2013-01-24T21:33:52 http://permalink.gmane.org/gmane.text.xml.forrest.devel/28731 <pre> I'd go with text/javascript - it's a reasonable default. It's worth noting that we serve it as 'application/javascript' because that's the default mime-type mapping for httpd[1]. --tim [1] - http://svn.apache.org/repos/asf/httpd/httpd/trunk/docs/conf/mime.types </pre> Tim Williams 2013-01-24T21:32:23 http://permalink.gmane.org/gmane.text.xml.forrest.devel/28730 <pre>According to this page: http://stackoverflow.com/questions/4101394/javascript-mime-type and many others on the net, application/javascript is the correct answer, but not accepted by MS IE ≤ 8. Which leaves us with text/javascript. But several places (including the above) argues that leaving it empty is fine, and the most compatible. I have no strong opinions, though, just that the present mime type definitely is wrong :) Sjur Den 24. jan 2013 kl. 22:12 skrev Tim Williams: </pre> Sjur Moshagen 2013-01-24T21:25:54 http://permalink.gmane.org/gmane.text.xml.forrest.devel/28729 <pre>I'd say text/javascript or application/javascript is the right answer. Omitting it feels pretty wrong though. --tim On Thu, Jan 24, 2013 at 4:01 PM, Sjur Moshagen &lt;sjurnm&lt; at &gt;mac.com&gt; wrote: </pre> Tim Williams 2013-01-24T21:12:14 http://permalink.gmane.org/gmane.text.xml.forrest.devel/28728 <pre>Hello, In the file '$FORREST_HOME/main/webapp/resources.xmap' there's the following match: &lt;map:match pattern="**skin/**.js"&gt; &lt;map:read src="{lm:skin.js.{2}}" mime-type="application/x-javascript" /&gt; &lt;/map:match&gt; x-javascript looks kind of strange and old. This is what wikipedia has to say about javascript mime type (http://en.wikipedia.org/wiki/Internet_media_type): «• application/javascript: ECMAScript/JavaScript; Defined in RFC 4329 (equivalent to application/ecmascript but with looser processing rules) It is not accepted in IE 8 or earlier - text/javascript is accepted but it is defined as obsolete in RFC 4329. The "type" attribute of the &lt;script&gt; tag inHTML5 is optional. In practice, ***omitting the media type of JavaScript programs is the most interoperable solution,*** since all browsers have always assumed the correct default even before HTML5.» (my emphasis) If there are no objections, I will just remove the mime type from that (and similar) match(es). Sjur </pre> Sjur Moshagen 2013-01-24T21:01:00 http://permalink.gmane.org/gmane.text.xml.forrest.devel/28727 <pre>To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at general&lt; at &gt;gump.apache.org. Project forrest-test-basic has an issue affecting its community integration. This issue affects 3 projects. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - forrest-test : Apache Forrest software is a publishing framework that trans... - forrest-test-basic : Apache Forrest software is a publishing framework that trans... - forrest-test-deploy-plugins : Apache Forrest software is a publishing framework that trans... Full details are available at: http://vmgump.apache.org/gump/public/forrest/forrest-test-basic/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -INFO- Failed with reason build failed The following work was performed: http://vmgump.apache.org/gump/public/forrest/forrest-test-basic/gump_work/build_forrest_forrest-test-basic.html Work Name: build_forrest_forrest-test-basic (Type: Build) Work ended in a state of : Failed Elapsed: 11 secs Command Line: /usr/lib/jvm/java-7-oracle/bin/java -Djava.awt.headless=true -Dbuild.sysclasspath=only -Xbootclasspath/p:/srv/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar:/srv/gump/public/workspace/xml-xerces2/build/xercesImpl.jar:/srv/gump/public/workspace/xml-xalan/build/xalan-unbundled.jar:/srv/gump/public/workspace/xml-xalan/build/serializer.jar org.apache.tools.ant.Main -Dgump.merge=/srv/gump/public/gump/work/merge.xml test-basic [Working Directory: /srv/gump/public/workspace/forrest/main] CLASSPATH: /usr/lib/jvm/java-7-oracle/lib/tools.jar:/srv/gump/public/workspace/forrest/tools/jetty/jetty-6.1.26.jar:/srv/gump/public/workspace/forrest/tools/jetty/jetty-util-6.1.26.jar:/srv/gump/public/workspace/forrest/tools/jetty/servlet-api-2.5-6.1.5.jar:/srv/gump/public/workspace/forrest/lib/core/chaperon-20040205.jar:/srv/gump/public/workspace/forrest/lib/core/ehcache-core-2.2.0.jar:/srv/gump/public/workspace/forrest/lib/core/slf4j-log4j12-1.5.11.jar:/srv/gump/public/workspace/forrest/lib/core/slf4j-api-1.5.11.jar:/srv/gump/public/workspace/forrest/lib/core/batik-all-1.6.jar:/srv/gump/public/workspace/forrest/lib/core/jing-20091111.jar:/srv/gump/public/workspace/forrest/build/xml-forrest.jar:/srv/gump/packages/apache-attic/avalon-framework-api-4.3.jar:/srv/gump/packages/apache-attic/a valon-framework-impl-4.3.jar:/srv/gump/packages/cocoon-2.1.x/cocoon-2.1.11.jar:/srv/gump/packages/cocoon-2.1.x/cocoon-asciiart-2.1.11.jar:/srv/gump/packages/cocoon-2.1.x/cocoon-auth-2.1.11.j ar:/srv/gump/packages/cocoon-2.1.x/cocoon-batik-2.1.11.jar:/srv/gump/packages/cocoon-2.1.x/cocoon-chaperon-2.1.11.jar:/srv/gump/packages/cocoon-2.1.x/cocoon-fop-2.1.11.jar:/srv/gump/packages/cocoon-2.1.x/cocoon-html-2.1.11.jar:/srv/gump/packages/cocoon-2.1.x/cocoon-linkrewriter-2.1.11.jar:/srv/gump/packages/cocoon-2.1.x/cocoon-lucene-2.1.11.jar:/srv/gump/packages/cocoon-2.1.x/cocoon-profiler-2.1.11.jar:/srv/gump/packages/cocoon-2.1.x/cocoon-template-2.1.11.jar:/srv/gump/packages/cocoon-2.1.x/cocoon-validation-2.1.11.jar:/srv/gump/packages/cocoon-2.1.x/cocoon-xsp-2.1.11.jar:/srv/gump/packages/apache-attic/excalibur-component-2.2.1.jar:/srv/gump/packages/apache-attic/excalibur-datasource-2.2.2.jar:/srv/gump/packages/apache-attic/excalibur-instrument-api-2.2.1.jar:/srv/gump/packages/apache-a ttic/excalibur-logger-2.2.1.jar:/srv/gump/packages/apache-attic/excalibur-pool-api-2.2.1.jar:/srv/gump/packages/apache-attic/excalibur-pool-impl-2.2.1.jar:/srv/gump/packages/apache-attic/exc alibur-pool-instrumented-2.2.1.jar:/srv/gump/packages/apache-attic/excalibur-sourceresolve-2.2.3.jar:/srv/gump/packages/apache-attic/excalibur-store-2.2.1.jar:/srv/gump/packages/apache-attic/excalibur-xmlutil-2.2.1.jar:/srv/gump/packages/apache-attic/excalibur-i18n-1.1.jar:/srv/gump/packages/apache-attic/excalibur-io-1.1.jar:/srv/gump/packages/apache-attic/excalibur-naming-1.0.jar:/srv/gump/packages/nekopull-0.2.4/nekopull.jar:/srv/gump/public/workspace/ant/dist/lib/ant.jar:/srv/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/srv/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/srv/gump/public/workspace/ant/dist/lib/ant-junit.jar:/srv/gump/public/workspace/ant/dist/lib/ant-swing.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/srv/gump/public/workspace/ant/dist/lib /ant-apache-xalan2.jar:/srv/gump/public/workspace/ant-contrib/target/ant-contrib-23012013.jar:/srv/gump/public/workspace/apache-commons/bcel/target/bcel-6.0-SNAPSHOT.jar:/srv/gump/public/wor kspace/commons-lang-2.x/target/commons-lang-2.7-SNAPSHOT.jar:/srv/gump/public/workspace/xml-commons/java/external/build/xml-apis-ext.jar:/srv/gump/packages/apache-attic/avalon-logkit-2.1.jar:commons-cli-gump-22012013.jar:/srv/gump/public/workspace/apache-commons/io/target/commons-io-2.5-SNAPSHOT.jar:commons-collections-gump-22012013.jar:commons-logging-gump-22012013.jar:commons-logging-api-gump-22012013.jar:/srv/gump/packages/dougLea/concurrent.jar:/srv/gump/packages/apache-attic/oro-2.0.8.jar:log4j-gump-22012013.jar:/srv/gump/public/workspace/xml-commons/java/build/resolver.jar:/srv/gump/public/workspace/apache-commons/jxpath/target/commons-jxpath-1.4-SNAPSHOT.jar --------------------------------------------- [copy] Copying 1 file to /srv/gump/public/workspace/forrest/build/test_skinned_site/build/site [echo] Copying main skin images to site ... [mkdir] Created dir: /srv/gump/public/workspace/forrest/build/test_skinned_site/build/site/skin/images [copy] Copying 20 files to /srv/gump/public/workspace/forrest/build/test_skinned_site/build/site/skin/images [copy] Copying 14 files to /srv/gump/public/workspace/forrest/build/test_skinned_site/build/site/skin/images [echo] Copying project skin images to site ... [copy] Warning: /srv/gump/public/workspace/forrest/main/src/documentation/skins/common/images does not exist. [copy] Warning: /srv/gump/public/workspace/forrest/main/src/documentation/skins/pelt/images does not exist. [echo] Copying main skin css and js files to site ... [copy] Copying 11 files to /srv/gump/public/workspace/forrest/build/test_skinned_site/build/site/skin [copy] Copied 4 empty directories to 3 empty directories under /srv/gump/public/workspace/forrest/build/test_skinned_site/build/site/skin [copy] Copying 4 files to /srv/gump/public/workspace/forrest/build/test_skinned_site/build/site/skin [echo] Copying project skin css and js files to site ... [copy] Warning: /srv/gump/public/workspace/forrest/main/src/documentation/skins/common does not exist. [copy] Warning: /srv/gump/public/workspace/forrest/main/src/documentation/skins/pelt does not exist. [echo] [echo] Finished copying the non-generated resources. [echo] Now Cocoon will generate the rest. [echo] [echo] [echo] Static site will be generated at: [echo] /srv/gump/public/workspace/forrest/build/test_skinned_site/build/site [echo] [echo] Cocoon will report the status of each document: [echo] - in column 1: *=okay X=brokenLink ^=pageSkipped (see FAQ). [echo] [java] Exception in thread "main" java.lang.NoClassDefFoundError: org/apache/commons/cli/Options [java] at org.apache.cocoon.Main.setOptions(Main.java:99) [java] at org.apache.cocoon.Main.main(Main.java:222) [java] Caused by: java.lang.ClassNotFoundException: org.apache.commons.cli.Options [java] at java.net.URLClassLoader$1.run(URLClassLoader.java:366) [java] at java.net.URLClassLoader$1.run(URLClassLoader.java:355) [java] at java.security.AccessController.doPrivileged(Native Method) [java] at java.net.URLClassLoader.findClass(URLClassLoader.java:354) [java] at java.lang.ClassLoader.loadClass(ClassLoader.java:423) [java] at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308) [java] at java.lang.ClassLoader.loadClass(ClassLoader.java:356) [java] ... 2 more [java] Java Result: 1 [echo] [echo] Copying broken links file to site root. [echo] BUILD FAILED /srv/gump/public/workspace/forrest/main/build.xml:428: The following error occurred while executing this line: /srv/gump/public/workspace/forrest/main/build.xml:430: The following error occurred while executing this line: /srv/gump/public/workspace/forrest/main/build.xml:450: The following error occurred while executing this line: /srv/gump/public/workspace/forrest/main/targets/site.xml:180: Warning: Could not find file /srv/gump/public/workspace/forrest/build/test_skinned_site/build/tmp/brokenlinks.xml to copy. Total time: 11 seconds --------------------------------------------- To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/forrest/forrest-test-basic/rss.xml - Atom: http://vmgump.apache.org/gump/public/forrest/forrest-test-basic/atom.xml ============================== Gump Tracking Only === Produced by Apache Gump(TM) version 2.3. Gump Run 11000023012013, vmgump.apache.org:vmgump:11000023012013 Gump E-mail Identifier (unique within run) #58. -- Apache Gump http://gump.apache.org/ [Instance: vmgump] </pre> Gump 2013-01-23T04:35:21 http://permalink.gmane.org/gmane.text.xml.forrest.devel/28726 <pre> Nice. The power of open source development. Last night i was just about to help with the deployment issue, when you managed to fix it. Great. -David </pre> David Crossley 2013-01-21T05:14:47 http://permalink.gmane.org/gmane.text.xml.forrest.devel/28725 <pre>Hello again, Den 18. jan 2013 kl. 15:04 skrev Sjur Moshagen: Request canceled. I managed to deploy the updated wiki plugin (as seen by the svn mails) by checking out a fresh copy of forrest, with no local modifications. I have tested the deployed plugin with different versions of forrest (svn HEAD and latest official release), and both are able to find the deployed plugin. It seems everything is fine. Sorry for the noise. Best, Sjur </pre> Sjur Moshagen 2013-01-18T14:38:44 http://permalink.gmane.org/gmane.text.xml.forrest.devel/28724 <pre>Hello all, Could some developer be kind and run 'ant deploy' in $FORREST_HOME/plugins/org.apache.forrest.plugin.input.wiki/ ? I have issues with my own instance of Forrest, and am not able to get a clean deploy through. There should be no issues with the plugin though. I need the latest dev version of that plugin online as soon as possible, so that I can start to rely on the availability of the new features for my colleagues. Thanks a lot in advance, Sjur </pre> Sjur Moshagen 2013-01-18T13:04:20 http://permalink.gmane.org/gmane.text.xml.forrest.devel/28723 <pre>Den 17. jan 2013 kl. 02:08 skrev David Crossley: It turned out to be a missing feature in the grammar. I have now implemented it, and it behaves as expected. I had to both tinker a bit with the grammar, and resolve some abiguity afterwards in the xsl processing (it is impossible for the tokeniser to know that a ':' at the end of a word is *not* a term definition separator, so I had to reconnect it to the preceding text if it was not inside an already established definition list). Thanks for following up, it inspired me to try once more, and that fixed it :) Ok, I will do that soon. Sjur </pre> Sjur Moshagen 2013-01-18T10:01:17 http://permalink.gmane.org/gmane.text.xml.forrest.devel/28722 <pre> I wonder if it is the "space" characters. The reference [1] shows no spaces. I reckon that it is fine to add whatever solution enables it to work for you. We can always issue a new version of the plugin later that fixes it differently. I reckon so. There is not enough activity to warrant separate versions. -David </pre> David Crossley 2013-01-17T00:08:42 http://permalink.gmane.org/gmane.text.xml.forrest.devel/28721 <pre>Hi all, I needed to fix some bugs (or missing features) in the wiki plugin, to better cope with the jspwiki format. So far I have only stored the changes locally in my project folder (thus the previous commit to fix the locationmap for finding resource files). Now I would like to move the changes to the plugin, but there are one change that I would like feedback on before I do this. The changes I have made are these: * I added support for formatting and links within table cells, so that tables now should behave as the jspwiki spec [1] says * I added support for definition lists (terms + definition), but *NOT* in accordance with the jspwiki spec The reason for not following the spec was that I could not get the Chaperon grammar (which is used to parse the jspwiki document and convert it to xml) to accept the syntax used by jspwiki. I don't know why, but to me it looks like a bug in the Chaperon lexer. The jspwiki syntax is: ; Term : definition My syntax is: #; Term ##: definition Not as elegant, but it works, and my implementation allows for links, formatting and breaks within the definition (which should be in accordance with the jspwiki syntax). Now the question(s): * is it ok with you if I commit these changes, even though one is with a different syntax than expected? I will of course update the documentation accordingly * it is said in the wiki plugin docs that we should keep the sources in sync with the Cocoon 2.1 block - but does that even apply for the syntax-breaking changes? Best regards, Sjur [1] http://www.jspwiki.org/wiki/TextFormattingRules </pre> Sjur Moshagen 2013-01-15T19:49:18 http://permalink.gmane.org/gmane.text.xml.forrest.devel/28720 <pre> [ https://issues.apache.org/jira/browse/FOR-1235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&amp;focusedCommentId=13550837#comment-13550837 ] David Crossley commented on FOR-1235: ------------------------------------- See r1425266 which added a "gump-plugins" target to our build which deploys the needed plugins. Declare any future others here. See r1425427 which forces gump to use those. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira </pre> David Crossley (JIRA 2013-01-11T05:24:15 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.text.xml.forrest.devel