gmane.text.xml.forrest.devel

[jira] Subscription: FOR-open-with-patch

2008-11-30T20:31:46

Issue Subscription Filter: FOR-open-with-patch (12 issues) Subscriber: rgardler Key Summary FOR-211 whole-site html and pdf: broken ext links https://issues.apache.org/jira/browse/FOR-211 FOR-969 Add sensible site navigation in DOAP plugin https://issues.apache.org/jira/browse/FOR-969 FOR-355 Improved PDF configurability (e.g., TOC, Page Numbers, logo) https://issues.apache.org/jira/browse/FOR-355 FOR-652 CSS Style Sheets need cleanup, optimization and better naming of elements https://issues.apache.org/jira/browse/FOR-652 FOR-998 [PATCH] Resolve empty cells. https://issues.apache.org/jira/browse/FOR-998 FOR-707 Document i18n features of Forrest https://issues.apache.org/jira/browse/FOR-707 FOR-412 use CSS for displaying list of Changes https://issues.apache.org/jira/browse/FOR-412 FOR-311 OOo Headings bug causes Forrest to fail https://issues.apache.org/jira/browse/FOR-311 FOR-934 i18n language override menu https://issues.apache.org/jira/browse/FOR-934 FOR-280 gather index terms from documents to create index page with links https://issues.apache.org/jira/browse/FOR-280 FOR-752 Forrestbot "build" workstage creates spurious "build/webapp/WEB-INF/logs" directory https://issues.apache.org/jira/browse/FOR-752 FOR-795 Navigation bars for easy access in long documents https://issues.apache.org/jira/browse/FOR-795

[RT] Requirements for Spring-based Forrest (forrest2)

Brian M Dube — 2008-11-29T00:56:12

I'd like to spend some time on a proof of concept version of Forrest without Cocoon, whether that's whiteboard/forrest2 or a new approach. One of the requirements, or at least functional tests, that has already been mentioned with respect to forrest2 is that the seed site must function correctly. I think this implies that current style plugins need to be supported. To support current plugins requires sitemap and locationmap implementations that don't depend on Cocoon. It looks difficult, but not impossible, to extract sitemap support from the Cocoon source. Is this the way to go? Implement support for sites and plugins as they exist now, and use a new format for new development? What are the other requirements to move away from Cocoon? Is there community interest to move away from Cocoon? Brian

Question about Images resolver in webapp mode

Antoine Robert — 2008-11-28T12:27:30

This message is about this issue : http://www.nabble.com/PDF-not-working-correctly-in-deployed-WAR-file-on-Tomcat-td15295911.html Hi, I'm using current release of forrest (0.8) and I have some trouble with having pictures displayed in War file on Tomcat. As you can read in the linked post, I tried many things. I was wondering if you were working on that or not . Thanks for your help.

ForrestBot build for forrest-sample-2 FAILED

2008-11-27T06:07:11

Automated build for forrest-sample-2 FAILED Log attached. ---------- Forrestbot run ended at 27 November 06:07 AM Using Forrest 0.9-dev Forrestbot administrator: Forrest developers ---------- [echo] ....... Forrest render START 2008-11-27 06:07:05 ... Rendering docs in /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2 check-java-version: [echo] This is apache-forrest-0.9-dev [echo] Using Java 1.4 from /usr/j2se/jre [echo] Using Apache Ant version 1.7.1 compiled on September 26 2008 from /export/opt/forrest-trunk/tools/ant init-props: [mkdir] Created dir: /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/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-sample-2/tmp [copy] Copying 1 file to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/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-sample-2/tmp/plugins-1.xml [get] local file date : Thu Sep 18 09:05:40 GMT+00:00 2008 [get] Not modified - so not downloaded [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-sample-2/tmp/plugins-2.xml [get] local file date : Thu Sep 25 19:05:25 GMT+00:00 2008 [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/forrest-sample-2/webapp/conf [copy] Copying 1 file to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp [copy] Copying 1 file to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp [copy] Copying 1 file to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp [copy] Copying 1 file to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp [copy] Copying 1 file to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/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/forrest-sample-2/tmp/plugins-1.xml... [xslt] Processing /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp/plugins-1.xml to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/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 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 [xslt] Processing /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp/output.xmap to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp/output.xmap.new [xslt] Loading stylesheet /export/opt/forrest-trunk/main/var/pluginMountSnippet.xsl [move] Moving 1 file to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/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-sample-2/tmp/locationmap.xml to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/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-sample-2/tmp [echo] -------------------------------------------------------------- Installing plugin: org.apache.forrest.plugin.internal.dispatcher -------------------------------------------------------------- check-plugin: [echo] org.apache.forrest.plugin.internal.dispatcher 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.internal.dispatcher in the different descriptor files [echo] Using the descriptor file /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp/plugins-1.xml... [xslt] Processing /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp/plugins-1.xml to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp/pluginlist2fetchbuild.xml [xslt] Loading stylesheet /export/opt/forrest-trunk/main/var/pluginlist2fetch.xsl findPlugin: [echo] Using the descriptor file /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp/plugins-2.xml... [xslt] Processing /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp/plugins-2.xml to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/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.internal.dispatcher [echo] Looking in local /export/opt/forrest-trunk/plugins [echo] Looking in local /export/opt/forrest-trunk/whiteboard/plugins [echo] Found ! init-build-compiler: echo-init: init: compile: jar: local-deploy: [echo] Locally deploying org.apache.forrest.plugin.internal.dispatcher [copy] Copying 121 files to /export/opt/forrest-trunk/build/plugins/org.apache.forrest.plugin.internal.dispatcher [copy] Copied 48 empty directories to 1 empty directory under /export/opt/forrest-trunk/build/plugins/org.apache.forrest.plugin.internal.dispatcher [copy] Copying 1 file to /export/opt/forrest-trunk/build/plugins/lib [copy] Copying 1 file to /export/opt/forrest-trunk/build/plugins/lib build: [echo] Plugin org.apache.forrest.plugin.internal.dispatcher 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-internal-plugin: [echo] Mounting internal plugin: org.apache.forrest.plugin.internal.dispatcher [xslt] Processing /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp/internal.xmap to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp/internal.xmap.new [xslt] Loading stylesheet /export/opt/forrest-trunk/main/var/pluginMountSnippet.xsl [move] Moving 1 file to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp configure-plugin-locationmap: [echo] Mounting plugin locationmap for org.apache.forrest.plugin.internal.dispatcher [xslt] Processing /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp/locationmap.xml to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/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-sample-2/tmp [echo] -------------------------------------------------------------- Installing plugin: org.apache.forrest.themes.core -------------------------------------------------------------- check-plugin: [echo] org.apache.forrest.themes.core 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.themes.core in the different descriptor files [echo] Using the descriptor file /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp/plugins-1.xml... [xslt] Processing /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp/plugins-1.xml to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp/pluginlist2fetchbuild.xml [xslt] Loading stylesheet /export/opt/forrest-trunk/main/var/pluginlist2fetch.xsl findPlugin: [echo] Using the descriptor file /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp/plugins-2.xml... [xslt] Processing /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp/plugins-2.xml to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/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.themes.core [echo] Looking in local /export/opt/forrest-trunk/plugins [echo] Looking in local /export/opt/forrest-trunk/whiteboard/plugins [echo] Found ! init-build-compiler: echo-init: init: compile: jar: local-deploy: [echo] Locally deploying org.apache.forrest.themes.core [copy] Copying 226 files to /export/opt/forrest-trunk/build/plugins/org.apache.forrest.themes.core [copy] Copied 28 empty directories to 4 empty directories under /export/opt/forrest-trunk/build/plugins/org.apache.forrest.themes.core build: [echo] Plugin org.apache.forrest.themes.core 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: [echo] No locationmap provided for plugin org.apache.forrest.themes.core init: -prepare-classpath: check-contentdir: examine-proj: validation-props: validate-xdocs: [echo] Oops, something broke

[jira] Created: (FOR-1132) the verbosity level for the catalog entity resolver has no effect for Ant target "validate-xdocs"

David Crossley (JIRA — 2008-11-27T06:04:46

the verbosity level for the catalog entity resolver has no effect for Ant target "validate-xdocs" ------------------------------------------------------------------------------------------------- Key: FOR-1132 URL: https://issues.apache.org/jira/browse/FOR-1132 Project: Forrest Issue Type: Bug Components: XML grammars & validation Affects Versions: 0.8, 0.7, 0.9-dev Reporter: David Crossley A project can use a CatalogManager.properties file to specify the verbosity level of the catalog entity resolver. This works fine during the phase of generating docs via Cocoon. However it has no effect when doing 'forrest validate-xdocs' i.e. via Ant. The directory which holds the CatalogManager.properties file needs to be on the classpath when the "xml commons resolver" is used by Ant.

[jira] Created: (FOR-1131) catalog entity resolver not working for use by projects

David Crossley (JIRA — 2008-11-27T05:28:44

catalog entity resolver not working for use by projects ------------------------------------------------------- Key: FOR-1131 URL: https://issues.apache.org/jira/browse/FOR-1131 Project: Forrest Issue Type: Bug Components: Core operations, XML grammars & validation Affects Versions: 0.9-dev Reporter: David Crossley Fix For: 0.9-dev Each project can utilise the catalog entity resolver to use local copies of DTDs. However a recent attempt to fix FOR-1120 at r700787, caused this facility to break.

[Fwd: problem using own DTD with current 0.9dev]

EMMEL Thomas — 2008-11-25T13:53:22

transfered from user to dev too! Hi, I should say: 'Never touch a running system...' I decided this morning to update my current svn copy of 0.9dev to test whether there are fixes within the pdf generation. Now, nothing works anymore :-/ One problem is that my own DTD cannot be found anymore, although it is proper registered in the catalog.xcat-file. It seems that forrest cannot find it since it doesn't look at the correct location... You can verify this by doing the following steps: mkdir tmp; cd tmp forrest seed cd src/documentation/resources/schema/ cp hello-v10.dtd helloxxx-v10.dtd now change the file catalog.xcat by replacing hello by helloxxx like this: next change back to the root of your forrest-dir and change src/documentation/content/xdocs/samples-b/custom.xml to reference this new dtd finally run forrest -v validate-xdocs you should get an error that helloxxx-v10.dtd cannot be found. If not, I am missing something serious. Regards Thomas

[jira] Subscription: FOR-open-with-patch

2008-11-23T20:31:45

[jira] Created: (FOR-1130) Please add Newton to list of example sites

Derek Baum (JIRA — 2008-11-21T14:44:44

Please add Newton to list of example sites ------------------------------------------ Key: FOR-1130 URL: https://issues.apache.org/jira/browse/FOR-1130 Project: Forrest Issue Type: Task Components: Example Sites Reporter: Derek Baum Priority: Trivial Please add Newton to the list of example sites. Name: Newton URL: http://newton.codecauldron.org catch-phrase: Distributed OSGi framework many of the examples on the Newton site are generated from Open Office .odt documents, and much of the site is built into a single PDF developers guide. We have configured site.xml so the table of contents in the PDF looks reasonable. Thanks, Derek

FOR-1108 on Mac

Tim Williams — 2008-11-21T02:01:51

Hey Devs- I'm seeing FOR-1108 on OSX Leopard. I would assume that JIRA is up to date but that would mean trunk has been broken for quite some time, so I thought I'd just ask before looking into it. It seems to have been reported only relative to a platform (windows) so I thought it weird to be seeing it too. Is the trunk still broken? https://issues.apache.org/jira/browse/FOR-1108 Thanks, --tim

[jira] Created: (FOR-1129) Cannot get variable 'plugin.xmap.output' in expression '{lm:plugin.xmap.output}'

Paul O'Connell (JIRA — 2008-11-20T11:54:44

Cannot get variable 'plugin.xmap.output' in expression '{lm:plugin.xmap.output}' -------------------------------------------------------------------------------- Key: FOR-1129 URL: https://issues.apache.org/jira/browse/FOR-1129 Project: Forrest Issue Type: Bug Components: Core operations Affects Versions: 0.8 Reporter: Paul O'Connell I extracted forrest 0.8 on windows xp, and ran the 'site' and 'seed' operations using the java 1.5.0_12 jre. I expectrd a default site to be created, but got the following error. After posting to the forrest mail group, it was recommended that i raise an issue. Regards, ------------------------------------- Seed operation Apache Forrest. Run 'forrest -projecthelp' to list options Buildfile: C:\projects\Libs\apache-forrest-0.8\bin\..\main\forrest.build.xml seed: Copying 80 files to C:\projects\Libs\apache-forrest-0.8\sites\java5 Copied 18 empty directories to 2 empty directories under C:\projects\Libs\apache-forrest-0.8\sites\java5 ------------------------------- ~~ Template project created! ~~ Here is an outline of the generated files: / # C:\projects\Libs\apache-forrest-0.8\sites\java5 /forrest.properties # Optional file describing your site layout /src/documentation/ # Doc-specific files /src/documentation/skinconf.xml # Info about your project used by the skin /src/documentation/content # Site content. /src/documentation/content/xdocs # XML content. /src/documentation/content/xdocs/index.xml # Home page /src/documentation/content/xdocs/site.xml # Navigation file for site structure /src/documentation/content/xdocs/tabs.xml # Skin-specific 'tabs' file. /src/documentation/content/xdocs/*.html,pdf # Static content files, may have subdirs /src/documentation/resources/images # Project images (logos, etc) # you can create other directories as needed (see forrest.properties) What to do now? - Render this template to static HTML by typing 'forrest'. View the generated HTML in a browser to make sure everything works. - Alternatively 'forrest run' and browse to http://localhost:8888/ live demo. - Start adding content in xdocs/ remembering to declare new files in site.xml - Follow the document http://forrest.apache.org/docs/your-project.html - Provide any feedback to dev< at >forrest.apache.org Thanks for using Apache Forrest ------------------------------- BUILD SUCCESSFUL Total time: 2 seconds Apache Forrest. Run 'forrest -projecthelp' to list options Buildfile: C:\projects\Libs\apache-forrest-0.8\bin\..\main\forrest.build.xml check-java-version: This is apache-forrest-0.8 Using Java 1.5 from p:\javasoft\jdk\1.5.0_12\jre fetch-plugins-descriptors: Fetching plugins descriptor: http://forrest.apache.org/plugins/plugins.xml Getting: http://forrest.apache.org/plugins/plugins.xml To: C:\projects\Libs\apache-forrest-0.8\sites\java5\build\tmp\plugins-1.xml local file date : Sun Apr 15 13:42:28 BST 2007 Error getting http://forrest.apache.org/plugins/plugins.xml to C:\projects\Libs\apache-forrest-0.8\sites\java5\build\tmp\plugins-1.xml Fetching plugins descriptor: http://forrest.apache.org/plugins/whiteboard-plugins.xml Getting: http://forrest.apache.org/plugins/whiteboard-plugins.xml To: C:\projects\Libs\apache-forrest-0.8\sites\java5\build\tmp\plugins-2.xml local file date : Sun Apr 15 13:42:28 BST 2007 Error getting http://forrest.apache.org/plugins/whiteboard-plugins.xml to C:\projects\Libs\apache-forrest-0.8\sites\java5\build\tmp\plugins-2.xml Plugin list loaded from http://forrest.apache.org/plugins/plugins.xml. Plugin list loaded from http://forrest.apache.org/plugins/whiteboard-plugins.xml. init-plugins: Copying 1 file to C:\projects\Libs\apache-forrest-0.8\sites\java5\build\tmp Copying 1 file to C:\projects\Libs\apache-forrest-0.8\sites\java5\build\tmp Copying 1 file to C:\projects\Libs\apache-forrest-0.8\sites\java5\build\tmp Copying 1 file to C:\projects\Libs\apache-forrest-0.8\sites\java5\build\tmp Copying 1 file to C:\projects\Libs\apache-forrest-0.8\sites\java5\build\tmp -------------------------------------------------------------- Installing plugin: org.apache.forrest.plugin.output.pdf -------------------------------------------------------------- check-plugin: org.apache.forrest.plugin.output.pdf is available in the build dir. Trying to update it... fetch-plugin: Trying to find the description of org.apache.forrest.plugin.output.pdf in the different descriptor files Using the descriptor file C:\projects\Libs\apache-forrest-0.8\sites\java5\build\tmp\plugins-1.xml... Processing C:\projects\Libs\apache-forrest-0.8\sites\java5\build\tmp\plugins-1.xml to C:\projects\Libs\apache-forrest-0.8\sites\java5\build\tmp\pluginlist2fetchbuild.xml Loading stylesheet C:\projects\Libs\apache-forrest-0.8\main\var\pluginlist2fetch.xsl get-local: Trying to locally get org.apache.forrest.plugin.output.pdf Looking in local C:\projects\Libs\apache-forrest-0.8/plugins Found ! local-deploy: Locally deploying org.apache.forrest.plugin.output.pdf Plugin org.apache.forrest.plugin.output.pdf deployed ! Ready to configure Fetch-plugin Ok, installing ! configure-output-plugin: Mounting output plugin: org.apache.forrest.plugin.output.pdf Processing C:\projects\Libs\apache-forrest-0.8\sites\java5\build\tmp\output.xmap to C:\projects\Libs\apache-forrest-0.8\sites\java5\build\tmp\output.xmap.new Loading stylesheet C:\projects\Libs\apache-forrest-0.8\main\var\pluginMountSnippet.xsl Moving 1 file to C:\projects\Libs\apache-forrest-0.8\sites\java5\build\tmp configure-plugin-locationmap: Mounting plugin locationmap for org.apache.forrest.plugin.output.pdf Processing C:\projects\Libs\apache-forrest-0.8\sites\java5\build\tmp\locationmap.xml to C:\projects\Libs\apache-forrest-0.8\sites\java5\build\tmp\locationmap.xml.new Loading stylesheet C:\projects\Libs\apache-forrest-0.8\main\var\pluginLmMountSnippet.xsl Moving 1 file to C:\projects\Libs\apache-forrest-0.8\sites\java5\build\tmp validate-xdocs: ...validated xdocs validate-skinconf: 1 file(s) have been successfully validated. ...validated skinconf validate-sitemap: ...validated project sitemap validate-skinchoice: ...validated existence of skin 'pelt' site: Copying the various non-generated resources to site. Warnings will be issued if the optional project resources are not found. This is often the case, because they are optional and so may not be available. Copying project resources and images to site ... Warning: C:\projects\Libs\apache-forrest-0.8\sites\java5\build\webapp\resources not found. Copying 2 files to C:\projects\Libs\apache-forrest-0.8\sites\java5\build\site\en Copying main skin images to site ... Created dir: C:\projects\Libs\apache-forrest-0.8\sites\java5\build\site\en\skin\images Copying 18 files to C:\projects\Libs\apache-forrest-0.8\sites\java5\build\site\en\skin\images Copying 14 files to C:\projects\Libs\apache-forrest-0.8\sites\java5\build\site\en\skin\images Copying project skin images to site ... Warning: C:\projects\Libs\apache-forrest-0.8\sites\java5\src\documentation\skins\common\images not found. Warning: C:\projects\Libs\apache-forrest-0.8\sites\java5\src\documentation\skins\pelt\images not found. Copying main skin css and js files to site ... Copying 11 files to C:\projects\Libs\apache-forrest-0.8\sites\java5\build\site\en\skin Copied 4 empty directories to 3 empty directories under C:\projects\Libs\apache-forrest-0.8\sites\java5\build\site\en\skin Copying 4 files to C:\projects\Libs\apache-forrest-0.8\sites\java5\build\site\en\skin Copying project skin css and js files to site ... Warning: C:\projects\Libs\apache-forrest-0.8\sites\java5\src\documentation\skins\common not found. Warning: C:\projects\Libs\apache-forrest-0.8\sites\java5\src\documentation\skins\pelt not found. Finished copying the non-generated resources. Now Cocoon will generate the rest. Static site will be generated at: C:\projects\Libs\apache-forrest-0.8\sites\java5\build\site\en Cocoon will report the status of each document: - in column 1: *=okay X=brokenLink ^=pageSkipped (see FAQ). ------------------------------------------------------------------------ cocoon 2.2.0-dev Copyright (c) 1999-2005 Apache Software Foundation. All rights reserved. Build: December 8 2005 (TargetVM=1.4, SourceVM=1.4, Debug=on, Optimize=on) ------------------------------------------------------------------------ * [1/0] [0/0] 0.406s 0b linkmap.html org.apache.cocoon.sitemap.PatternException: Cannot get variable 'plugin.xmap.output' in expression '{lm:plugin.xmap.output}' at org.apache.cocoon.components.treeprocessor.variables.PreparedVariableResolver.processModule(PreparedVariableResolver.java:250) at org.apache.cocoon.components.treeprocessor.variables.PreparedVariableResolver.resolve(PreparedVariableResolver.java:197) at org.apache.cocoon.components.treeprocessor.sitemap.SelectNode.invoke(SelectNode.java:77) at org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:77) at org.apache.cocoon.components.treeprocessor.sitemap.PipelineNode.invoke(PipelineNode.java:155) at org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:77) at org.apache.cocoon.components.treeprocessor.sitemap.PipelinesNode.invoke(PipelinesNode.java:95) at org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process(ConcreteTreeProcessor.java:292) at org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process(ConcreteTreeProcessor.java:223) at org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreeProcessor.java:289) at org.apache.cocoon.Cocoon.process(Cocoon.java:557) at org.apache.cocoon.bean.CocoonWrapper.getPage(CocoonWrapper.java:426) at org.apache.cocoon.bean.CocoonBean.processTarget(CocoonBean.java:496) at org.apache.cocoon.bean.CocoonBean.process(CocoonBean.java:357) at org.apache.cocoon.Main.main(Main.java:311) Caused by: org.apache.avalon.framework.configuration.ConfigurationException: Unable to build LocationMap. at org.apache.forrest.locationmap.LocationMapModule.loadConfiguration(LocationMapModule.java:148) at org.apache.forrest.locationmap.LocationMapModule.getLocationMap(LocationMapModule.java:105) at org.apache.forrest.locationmap.LocationMapModule.getAttribute(LocationMapModule.java:203) at org.apache.cocoon.components.treeprocessor.variables.PreparedVariableResolver.processModule(PreparedVariableResolver.java:246) ... 14 more Caused by: org.apache.excalibur.source.SourceException: Cannot get input stream for cocoon://locationmap.xml at org.apache.cocoon.components.source.impl.SitemapSource.getInputStream(SitemapSource.java:184) at org.apache.forrest.locationmap.LocationMapModule.loadConfiguration(LocationMapModule.java:144) ... 17 more Caused by: org.apache.cocoon.ResourceNotFoundException: Resource not found. at - file:/C:/projects/Libs/apache-forrest-0.8/main/webapp/./sitemap.xmap:402:72 at org.apache.cocoon.components.source.impl.SitemapSource.init(SitemapSource.java:313) at org.apache.cocoon.components.source.impl.SitemapSource.(SitemapSource.java:146) at org.apache.cocoon.components.source.impl.SitemapSourceFactory.getSource(SitemapSourceFactory.java:65) at org.apache.cocoon.components.source.CocoonSourceResolver.resolveURI(CocoonSourceResolver.java:159) at org.apache.cocoon.components.source.CocoonSourceResolver.resolveURI(CocoonSourceResolver.java:189) at org.apache.forrest.locationmap.LocationMapModule.getLocationMap(LocationMapModule.java:95) ... 16 more X [0] linkmap.htmlBROKEN: URI not found: Cannot get variable 'plugin.xmap.output' in expression '{lm:plugin.xmap.output}' Total time: 0 minutes 4 seconds, Site size: 0 Site pages: 1 Java Result: 1 Copying broken links file to site root. Copying 1 file to C:\projects\Libs\apache-forrest-0.8\sites\java5\build\site\en BUILD FAILED C:\projects\Libs\apache-forrest-0.8\main\targets\site.xml:180: Error building site. There appears to be a problem with your site build. Read the output above: * Cocoon will report the status of each document: - in column 1: *=okay X=brokenLink ^=pageSkipped (see FAQ). * Even if only one link is broken, you will still get "failed". * Your site would still be generated, but some pages would be broken. - See C:\projects\Libs\apache-forrest-0.8\sites\java5\build\site\en/broken-links.xml Total time: 50 seconds

Forrest friendly searching

Tim Williams — 2008-11-20T02:06:39

I've been playing around with Google's Custom Search and thought I'd use Forrest as my playground since I have a good idea of what I think "good" results are. Anyway, I haven't added a whole lot of customization or refinements to it but think it's already fairly useful nonetheless. http://www.google.com/coop/cse?cx=014207783617196158741:fgpzn29ywzq e.g. http://www.google.com/cse?cx=014207783617196158741%3Afgpzn29ywzq&q=dispatcher Let me know what you think and let me know if you want to contribute... btw, i just picked a reasonable name, if it violates some rule, let me know... --tim

[jira] Subscription: FOR-open-with-patch

2008-11-16T20:30:46

[Announce] Call For Papers opens for ApacheCon US 2009

David Crossley — 2008-11-13T23:20:09

----- Forwarded message from "William A. Rowe, Jr." apache.org> ----- If you have only 30 seconds to read this; Join us in celebrating the ASF's 10th Anniversary at ApacheCon! The Call for Papers is now open for ApacheCon US 2009, taking place 2-6 November in Oakland, California. Proposals are being accepted at http://us.apachecon.com/c/acus2009/cfp/ and can be revised at anytime until the submissions closing deadline of 28 February 2009. In addition, sponsorship opportunities for both ApacheCon EU 2009/Amsterdam and ApacheCon US 2009/Oakland are available. Please contact Delia Frees at delia< at >apachecon.com for further information. Please, read on... ******* ApacheCon Celebrates the ASF's 10th Anniversary in Oakland, California, 2-6 November 2009 Call for Papers Opens for ApacheCon US 2009 The Apache Software Foundation (ASF) invites submissions to its official user and developer conference, taking place 2-6 November 2009 at the Oakland Convention Center and Marriott Hotel. ApacheCon serves as a forum for showcasing the ASF's latest projects, members, and community initiatives. Offering unparalleled educational opportunities, ApacheCon's presentations, hands-on trainings, and sessions address key technology, development, business/community, and licensing issues in Open Source. The wide range of activities offered at ApacheCon promotes the exchange of ideas amongst ASF Members, committers, innovators, developers, vendors, and users interested in the future of Open Source technology. The conference program includes peer-reviewed sessions, trainings/workshops, and select invited keynote presentations and speakers. Conference Themes and Topics Building on ten years of success, ApacheCon returns to the Bay Area for the 10th anniversary of the Apache Software Foundation. Comprising some of the most active and recognized developers in the Open Source community, ApacheCon provides an influential platform for dialogue between Open Source developers and users, traversing a wide range of ideas, expertise, and personalities. ApacheCon welcomes submissions across many fields, geographic locations, and areas of development. The breadth of the Apache community lends itself to conference content that is somewhat loosely-structured, with common themes of interest addressing groundbreaking technologies and emerging trends, best practices (from development to deployment), case studies and lessons learned (tips, tools, and tricks). In addition, ApacheCon will continue to offer its highly popular, two-day intensive trainings; certifications of completion will be distributed to those who fulfill all the training requirements. Topics appropriate for submission are manifold, and may include but are not restricted to: Apache HTTP server (installation, configuration, migration, and more); ASF-wide projects (including Lucene, Hadoop, Jackrabbit, and Maven); Scripting languages and dynamic content (such as Java, Perl, Python, Ruby, XSL, and PHP); Security and e-commerce (performance tuning, load balancing and high availability); New technologies (including broader initiatives such as Web Services and Web 2.0); ASF-Incubated projects (such as Sling, UIMA, and Shindig); and Business/Community issues (Open Source driven business models, open development, enterprise adoption, and more). Submission Guidelines Submissions must include; ??? Session title - Speaker name - Speaker biography - Session description - Format and duration - Audience expertise level Full details are available online on the CFP page at [WWW] http://us.apachecon.com/c/acus2009/cfp/ Types of Presentations; - Trainings/Workshops - General Sessions - Case Studies/Industry Profiles - Corporate Showcases & Demonstrations - Fast Feather (short) sessions - Birds of a Feather discussions - Invited Keynotes/Panels/Speakers Pre-Conference Trainings/Workshops Held on the first two days of the conference (2-3 November 2009), ApacheCon trainings are available at a registration fee beyond the regular conference fee. Proposals may be submitted for half-day (3 hours), full-day (6 hours), or two-day (12 hours) training sessions. These proposed tutorials should be aimed at providing in-depth, hands-on development experience or related continuing education. Training submissions are welcome at beginner, intermediate, and expert levels. General Sessions include presentations on practical development applications, insight into high-interest projects, best practices and key advances, overcoming implementation challenges, and industry innovations. Especially welcome are submissions that extend participants' understanding the role of ASF projects and their influence on the Open Source community at large. General Sessions are scheduled for 50 minutes and are accessible to all conference delegates. Case Study/Industry Profile Practitioners are invited to submit presentations that focus on how implementing particular ASF technologies led to improved products/solutions, service offerings, changes in work practices, among other successes. Proposals that highlight overcoming interesting challenges in application design and developing innovative frameworks using multiple ASF projects are particularly encouraged. NOTE: Marketing-oriented submissions aimed at promoting specific organizations or products will not be accepted. Invited Keynotes/Panels/Speakers Each conference the ApacheCon Planning team invites select presenters dealing with engaging, dialectical, and challenging subjects to present in keynote and/or panel formats. Topics include cutting-edge technology development, industry leadership, hot or emerging trends, opinions on controversial issues, insight on technology paradigms, and contrasting viewpoints in complementary professional areas. Those interested in suggesting a candidate for an invited speaker opportunity should submit a brief proposal with the speaker's name, affiliation, background/bio, overview of topics of interest, and contact information. Birds of a Feather (BoF) sessions and Fast Feather Track talks are selected by separate processes, nearer to the beginning of the conference. Proposals are now being accepted at http://us.apachecon.com/c/acus2009/cfp/ and can be revised at anytime until the submissions closing deadline of 28 February 2009. In addition, sponsorship opportunities for both ApacheCon EU 2009/Amsterdam and ApacheCon US 2009/Oakland are available. Please contact Delia Frees at delia< at >apachecon.com for further information. ApacheCon US 2009 is co-produced by the Apache Software Foundation and Stone Circle Productions. The ApacheCon Planning team comprises ASF Members from all over the world working on a wholly-volunteer basis. For more information, visit http://us.apachecon.com/c/acus2009/ ----- End forwarded message -----

[jira] Subscription: FOR-open-with-patch

2008-11-09T20:30:45

ApacheCon live video streaming available; keynotes and Apache 101 are free

David Crossley — 2008-11-04T22:32:42

Can't make ApacheCon this week in New Orleans? You can still watch all the keynotes, Apache 101 sessions, and system administration track in live video streams: http://streaming.linux-magazin.de/en/program_apacheconus08.htm?ann Keynotes and the Apache 101 lunchtime sessions are free; the full sysadmin track, including httpd performance, security, and server stack administration talks are available for a fee. Keynotes include: - David Recordon, Six Apart (Wednesday 09:30) "Learning from Apache to create Open Specifications" - Shahani Markus Weerawarana, Ph.D. (Thursday 11:30) "Standing on the Shoulders of Giants" - Sam Ramji, Microsoft (Friday 11:30) "struct.new("future", :open, :microsoft)" Reminder: New Orleans is CST or UTC/GMT -6 hours. Advance notice: ApacheCon EU 2009 returns to Amsterdam, 23-27 March. We had a great response to our CFP and look forward to announcing the schedule in the next month. -------------------------------------------

[jira] Subscription: FOR-open-with-patch

2008-11-02T20:30:44

[jira] Subscription: FOR-open-with-patch

2008-10-26T19:30:45

[jira] Subscription: FOR-open-with-patch

2008-10-19T19:30:47

[jira] Created: (FOR-1128) FAQs in Howto docs have auto-generated id< at > rather than source-specified identifier

David Crossley (JIRA — 2008-10-15T00:04:44

FAQs in Howto docs have auto-generated id< at > rather than source-specified identifier ---------------------------------------------------------------------------------- Key: FOR-1128 URL: https://issues.apache.org/jira/browse/FOR-1128 Project: Forrest Issue Type: Bug Components: Core operations Reporter: David Crossley FAQ sections in Howto documents are missing the "id" attribute that was set in the source document, and instead just has the generated default id.

[jira] Subscription: FOR-open-with-patch

2008-10-12T19:30:44