Thorsten Scherler a écrit :
My test forrest.properties (snippets):
#********************************************************
# code name: views
#********************************************************
# code name: (views-)themer
# views is using a fallback mechanism for theming.
# Themes are structured and transformed through templates.
# You can configure the theme name and its extension here
#####################################
# *theme* aka (also known as) {project:theme}
project.theme=pelt
# *theme-extension* aka {project:theme-ext}
# project.theme-extension=.fv
#####################################
# *description*
# Forrest will resolve which (view-) template is responsible
# for the request with the help of themes.
#
# If no (view-) template (first choice or fallback) can be found,
# the structurer will return the default fallback
# ({defaults:view-themes}/{defaults:theme}{defaults:theme-ext}).
#
# Example (default.fv):
# 1.request: index
# First choice: index.{project:theme-ext} = index.fv
# First/last fallback: {project:theme}{project:theme-ext} = default.fv
#
# 2.request: sample/index
# First choice: sample/index.fv
# First fallback: sample/default.fv
# Last fallback: default.fv
#
# 3.request: sample/subdir/index
# First choice: sample/subdir/index.fv
# First fallback: sample/subdir/default.fv
# Second fallback: sample/default.fv
# Last fallback: default.fv
# ...
# The parent (view-) template inherits to its children until a child
# is overriding this template. This fallback templating can be
# used for directories (default.fv) and/or files (*.fv).
# That means that the root view is the
# default view as long no other view can be found in the requested
child.
##########################################
# *advanced configuration* - you can specify which plugins you want
# use internal.
#project.themer=
${forrest.home}/build/plugins/org.apache.forrest.plugin.output.themes
#project.stucturer=
${forrest.home}/build/plugins/org.apache.forrest.plugin.internal.structurer
# depreceated:
# ...
project.required.plugins=org.apache.forrest.plugin.output.themes,org.apache.forrest.plugin.internal.structurer,org.apache.forrest.plugin.input.viewHelper.xhtml.ls
El jue, 13-10-2005 a las 16:38 +0200, Cyriaque Dupoirieux escribió:
Thorsten Scherler a écrit :
Done
Commit de la revisión 320775.
I just deleted the themer and check it out again. ;-)
I had finished to apply to patch :-( ...
Sorry.
It's not working with me, is there a problem with the
commons-jxpath-*-.jar version, which must I use ?
? lib/core/commons-jxpath-1.2.jar
What is the error?
D:\duc\stdViews>forrest
Apache Forrest. Run 'forrest -projecthelp' to list options
...
check-java-version:
This is apache-forrest-0.8-dev
Using Java 1.4 from C:\j2sdk1.4.1_02\jre
...
validate-skinchoice:
validated existence of skin 'leather-dev'
site:
...
Note that there are various reasons for "build failed" messages.
* 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.
* Please check the file:
D:\duc\stdViews\build\tmp\brokenlinks.xml
for any broken links in the generated site.
------------------------------------------------------------------------
cocoon 2.2.0-dev
Copyright (c) 1999-2005 Apache Software Foundation. All rights reserved.
Build: September 19 2005 (TargetVM=1.4, SourceVM=1.3, Debug=on, Optimize=on)
------------------------------------------------------------------------
X [0] linkmap.html BROKEN:
D:\duc\forrest\build\plugins\org.apache.forrest.plugin.internal.structurer\linkmap.xma
p (Le fichier spÚcifiÚ est introuvable)
Total time: 0 minutes 2 seconds, Site size: 0 Site pages: 0
BUILD FAILED
D:\duc\forrest\main\targets\site.xml:41: Java returned: 1
Total time: 23 seconds
Cyriaque,
salu2
