You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@forrest.apache.org by Eike Stepper <st...@esc-net.de> on 2004/06/19 16:02:22 UTC
can i use the trunk?
hi,
i'm quite new to forrest and had just managed to build
a first small site with the forrest-0.5.1-bin release. now
i have tried to use the trunk version of forrest from svn.
it appears that not all of the raw files are copied to the
build folder, but only the ones directly referenced by some
xdocs. that is fatal for my javadocs.
is there an undocumented switch?
btw. is there a place where i can tweak the generated pdfs?
(their appearance is rather evil, no margins...)
thanks
/eike
Re: can i use the trunk?
Posted by David Crossley <cr...@apache.org>.
Eike Stepper wrote:
> David Crossley schrieb:
> > Eike Stepper wrote:
> > > i'm quite new to forrest and had just managed to build
> > > a first small site with the forrest-0.5.1-bin release. now
> > > i have tried to use the trunk version of forrest from svn.
> >
> > This can certainly be done. Have you followed the
> > document called upgrading_06.html ?
>
> hmm, not very informative ;-(
Sure - it is a document in progress :-)
I was asking if you had at least seen the document,
because there are various issues that you need
to consider if you are upgrading from 0.5.1
> it only states that there is no more copying at all,
> what is definitely wrong for "forrest site" or "forrest".
> i suppose only "forrest run" is meant...
>
> > > it appears that not all of the raw files are copied to the
> > > build folder, but only the ones directly referenced by some
> > > xdocs.
> >
> > There should be no copying at all. If a few things are
> > still being copied, then they are glitches that we are
> > gradually fixing in the build process.
>
> actually the following appears to happen:
>
> project.content-dir=src
> project.raw-content-dir=${project.content-dir}/content/raw
> project.xdocs-dir=${project.content-dir}/content/xdocs
>
> all javadocs are copied from src/content/raw/docs/api to
> build/site/raw/docs/api, what is wrong. these files are not
> referenced from the (xdoc-) generated html-files.
>
> only those javadocs that are directly referenced from xdocs
> are copied to build/site/docs/api and would be reachable
> through the generated links. but most of the files are missing
> including the frameset files, so nothing is displayed.
Try adding a menu entry in your site.xml to point to
the top-level of your api docs.
--David
Re: can i use the trunk?
Posted by Eike Stepper <st...@esc-net.de>.
"David Crossley" <cr...@apache.org> schrieb im Newsbeitrag news:1087822108.1555.2429.camel@ighp...
> Eike Stepper wrote:
> > i'm quite new to forrest and had just managed to build
> > a first small site with the forrest-0.5.1-bin release. now
> > i have tried to use the trunk version of forrest from svn.
>
> This can certainly be done. Have you followed the
> document called upgrading_06.html ?
hmm, not very informative ;-(
it only states that there is no more copying at all,
what is definitely wrong for "forrest site" or "forrest".
i suppose only "forrest run" is meant...
> > it appears that not all of the raw files are copied to the
> > build folder, but only the ones directly referenced by some
> > xdocs.
>
> There should be no copying at all. If a few things are
> still being copied, then they are glitches that we are
> gradually fixing in the build process.
actually the following appears to happen:
project.content-dir=src
project.raw-content-dir=${project.content-dir}/content/raw
project.xdocs-dir=${project.content-dir}/content/xdocs
all javadocs are copied from src/content/raw/docs/api to
build/site/raw/docs/api, what is wrong. these files are not
referenced from the (xdoc-) generated html-files.
only those javadocs that are directly referenced from xdocs
are copied to build/site/docs/api and would be reachable
through the generated links. but most of the files are missing
including the frameset files, so nothing is displayed.
here is the console output:
Apache Forrest. Run 'forrest -projecthelp' to list options
Buildfile: C:\develop\tools\forrest\src\core\forrest.build.xml
init-props:
Loading project specific properties from C:\develop\workspace\de.escnet.net4j.docs\forrest.properties
Loading user specific properties from C:\Dokumente und Einstellungen\Stepper\forrest.properties
Loading default properties from C:\develop\tools\forrest\src\core\context\default-forrest.properties
Created dir: C:\develop\workspace\de.escnet.net4j.docs\build\tmp
Reading filters from C:\develop\workspace\de.escnet.net4j.docs\build\tmp\projfilters.properties
forrest.basic.jvmargs:-Dproject.home="C:\develop\workspace\de.escnet.net4j.docs" -Dforrest.home="C:\develop\tools\forrest\src\core"
echo-settings:
------------------------------------------------
| Forrest template run.
| Running from ${forrest.home} = C:\develop\tools\forrest\src\core
| Working on ${project.home} = C:\develop\workspace\de.escnet.net4j.docs
------------------------------------------------
| //where to put the result
| project.site-dir = C:\develop\workspace\de.escnet.net4j.docs\build\site
| //uri to start crawling/generation process
| project.start-uri = index.html
| //cocoon.xconf location
| project.configfile = C:\develop\workspace\de.escnet.net4j.docs\build\webapp/WEB-INF/cli.xconf
| //logkit.xconf location
| project.logkitfile = C:\develop\workspace\de.escnet.net4j.docs\build\webapp/WEB-INF/logkit.xconf
| //temp dir to throw stuff in (i.e. work and ctxt)
| project.temp-dir = C:\develop\workspace\de.escnet.net4j.docs\build\tmp
| //temp working directory for generation process
| project.cocoon-work-dir = C:\develop\workspace\de.escnet.net4j.docs\build\tmp\cocoon-work
| //temp context directory for generation process
| project.webapp = C:\develop\workspace\de.escnet.net4j.docs\build\webapp
| //debuglevel for logging (DEBUG, INFO, WARN, ERROR, FATAL_ERROR)
| project.debuglevel = ERROR
| //file for list of broken links
| project.brokenlinkfile = C:\develop\workspace\de.escnet.net4j.docs\build\brokenlinks.xml
| //check if you have tools.jar installed
| tools.jar.present = true
------------------------------------------------
| The following properties could be removed from future builds:
| //which skin to apply
| project.skin = tigris-style
| //where your documentation xml is
| project.content-dir = C:\develop\workspace\de.escnet.net4j.docs\src
------------------------------------------------
bare-context:
____________________________________
Using skin tigris-style
____________________________________
Created dir: C:\develop\workspace\de.escnet.net4j.docs\build\webapp
Copying 479 files to C:\develop\workspace\de.escnet.net4j.docs\build\webapp
Created dir: C:\develop\workspace\de.escnet.net4j.docs\build\webapp\WEB-INF\lib
validate-xdocs:
12 file(s) have been successfully validated.
...validated xdocs
validate-skinconf:
1 file(s) have been successfully validated.
...validated skinconf
validate-sitemap:
...validated sitemap
validate-skinchoice:
...validated existence of skin 'tigris-style'
copy-conf:
Copying 1 file to C:\develop\workspace\de.escnet.net4j.docs\build\webapp\WEB-INF
upgrade-skinconf:
Processing C:\develop\workspace\de.escnet.net4j.docs\src\skinconf.xml to
C:\develop\workspace\de.escnet.net4j.docs\build\webapp\skinconf.xml
Loading stylesheet C:\develop\tools\forrest\src\core\context\resources\stylesheets\upgrade-skinconf.xsl
copy-status:
Copying 1 file to C:\develop\workspace\de.escnet.net4j.docs\build\webapp
site:
Created dir: C:\develop\workspace\de.escnet.net4j.docs\build\tmp\cocoon-work
Copying 260 files to C:\develop\workspace\de.escnet.net4j.docs\build\site
------------------------------------------------------------------------
cocoon 2.1.5
Copyright (c) 1999-2004 Apache Software Foundation. All rights reserved.
------------------------------------------------------------------------
CatalogManager.properties: catalogs not found.
22.06.2004 10:21:38 org.apache.jcs.engine.control.CompositeCacheConfigurator setDefaultAuxValues
INFO: setting defaults to DC
22.06.2004 10:21:38 org.apache.jcs.engine.control.CompositeCacheConfigurator setDefaultCompositeCacheAttributes
INFO: setting defaultCompositeCacheAttributes to [ useLateral = true, useRemote = true, useDisk = true, maxObjs = 100,
maxSpoolPerRun = -1 ]
22.06.2004 10:21:38 org.apache.jcs.config.OptionConverter instantiateByKey
WARNUNG: Could not find value for key jcs.default.elementattributes
22.06.2004 10:21:38 org.apache.jcs.engine.control.CompositeCacheConfigurator parseElementAttributes
WARNUNG: Could not instantiate eAttr named 'jcs.default.elementattributes', using defaults.
22.06.2004 10:21:38 org.apache.jcs.engine.control.CompositeCacheConfigurator setDefaultElementAttributes
INFO: setting defaultElementAttributes to [ IS_LATERAL = false, IS_SPOOL = false, IS_REMOTE = false, IS_ETERNAL = true,
MaxLifeSeconds = -1, IdleTime = -1, CreateTime = 1087892498890, LastAccessTime = 1087892498890, getTimeToLiveSeconds() = -1000,
createTime = 1087892498890 ]
22.06.2004 10:21:38 org.apache.jcs.config.OptionConverter instantiateByKey
WARNUNG: Could not find value for key jcs.system.groupIdCache.elementattributes
22.06.2004 10:21:38 org.apache.jcs.engine.control.CompositeCacheConfigurator parseElementAttributes
WARNUNG: Could not instantiate eAttr named 'jcs.system.groupIdCache.elementattributes', using defaults.
22.06.2004 10:21:38 org.apache.jcs.engine.memory.lru.LRUMemoryCache initialize
INFO: initialized LRUMemoryCache for groupIdCache
22.06.2004 10:21:38 org.apache.jcs.engine.control.CompositeCache <init>
INFO: Constructed cache with name: groupIdCache
22.06.2004 10:21:39 org.apache.jcs.auxiliary.disk.indexed.IndexedDiskCache <init>
INFO: Cache file root directory: C:\develop\workspace\de.escnet.net4j.docs\build\webapp\..\tmp\cocoon-work
22.06.2004 10:21:39 org.apache.jcs.config.OptionConverter instantiateByKey
WARNUNG: Could not find value for key jcs.region.main.elementattributes
22.06.2004 10:21:39 org.apache.jcs.engine.control.CompositeCacheConfigurator parseElementAttributes
WARNUNG: Could not instantiate eAttr named 'jcs.region.main.elementattributes', using defaults.
22.06.2004 10:21:39 org.apache.jcs.engine.memory.lru.LRUMemoryCache initialize
INFO: initialized LRUMemoryCache for main
22.06.2004 10:21:39 org.apache.jcs.engine.control.CompositeCache <init>
INFO: Constructed cache with name: main
22.06.2004 10:21:39 org.apache.jcs.auxiliary.disk.indexed.IndexedDiskCache <init>
INFO: Cache file root directory: C:\develop\workspace\de.escnet.net4j.docs\build\webapp\..\tmp\cocoon-work
^ docs/
* [1/23] [23/26] 4.125s 11.5Kb index.html
* [2/22] [0/0] 0.047s 8.1Kb docs/Multiplexing.gif
^ docs/
* [3/21] [0/21] 1.094s 5.9Kb download.html
^ docs/
* [4/21] [1/23] 1.828s 9.1Kb links.html
^ docs/
* [5/20] [0/21] 0.828s 5.8Kb docs/implementation.html
* [6/19] [0/0] 0.281s 817b skin/print.css
* [7/18] [0/0] 0.047s 4.2Kb images/net4j.gif
^ docs/
* [8/17] [0/21] 1.234s 33.0Kb license.html
* [9/16] [0/0] 0.453s 5.5Kb skin/forrest.css
* [10/15] [0/0] 0.078s 1.7Kb skin/menu.js
* [11/14] [0/0] 0.031s 6.4Kb skin/breadcrumbs.js
^ docs/
* [12/18] [5/30] 1.078s 14.5Kb docs/index.html
* [13/17] [0/0] 0.047s 26.2Kb docs/api/de/escnet/net4j/impl/SocketConnector.html
* [14/16] [0/0] 0.016s 17.8Kb /docs/api/de/escnet/net4j/Connector.html
^ docs/
* [15/21] [6/27] 0.812s 11.2Kb docs/architecture.html
* [16/20] [0/0] 0.016s 12.3Kb docs/SystemDecomposition.gif
* [17/19] [0/0] 0.031s 3.1Kb docs/Executors.gif
* [18/18] [0/0] 0.016s 3.0Kb docs/Acceptors.gif
* [19/17] [0/0] 0.047s 20.2Kb docs/ConnectorHierarchy.gif
* [20/16] [0/0] 0.015s 3.1Kb docs/Protocols.gif
* [21/15] [0/0] 0.031s 11.6Kb images/berlios.bmp
^ docs/
* [22/14] [0/21] 1.391s 11.5Kb docs/glossary.html
* [23/13] [0/0] 0.031s 4.9Kb docs/Connectors.gif
* [24/12] [0/0] 0.032s 1.8Kb images/built-with-forrest-button.png
* [25/11] [0/0] 0.015s 7.6Kb docs/PushService.gif
* [26/10] [0/0] 0.016s 1.1Kb skin/images/vcss.png
* [27/9] [0/0] 0.0s 923b docs/api/index.html
* [28/8] [0/0] 0.032s 21.8Kb docs/api/de/escnet/net4j/impl/EmbeddedConnector.html
* [29/7] [0/0] 0.015s 1.6Kb images/eclipse_bckgr_logo_fc_xsm.jpg
* [30/6] [0/0] 0.032s 9.0Kb docs/SocketAndEmbedded.gif
* [31/5] [0/0] 0.015s 2.5Kb skin/tigris.js
* [32/4] [0/0] 0.047s 11.8Kb docs/ContainerSetup.gif
^ docs/
* [33/3] [0/21] 0.781s 6.2Kb faq.html
Copying 19 files to C:\develop\workspace\de.escnet.net4j.docs\build\site\skin\images
* [34/2] [0/0] 0.422s 10.1Kb docs/api/de/escnet/net4j/merlin/MerlinEmbedder.html
* [35/1] [0/0] 0.047s 2.8Kb skin/images/valid-html401.png
* [36/0] [0/0] 0.016s 3.6Kb images/esc.gif
Copying 62 files to C:\develop\workspace\de.escnet.net4j.docs\build\site\skin\images
22.06.2004 10:21:55 org.apache.jcs.engine.CacheEventQueue destroy
INFO: Cache event queue destroyed: listenerId=118, cacheName=main
22.06.2004 10:21:55 org.apache.jcs.auxiliary.disk.indexed.IndexedDiskCache doUpdate
SCHWERWIEGEND: Failure updating element, cacheName: main, key:
PK_G-file-cocoon://abs-linkmap?pipelinehash=278467903521696551_T-xslt-file:/C:/develop/tools/forrest/src/core/context/resources/styl
esheets/relativize-linkmap.xsl;site-root=http://net4j.berlios.de;path=docs/index.html
java.lang.InterruptedException
at java.lang.Object.wait(Native Method)
at org.apache.jcs.utils.locking.ReadWriteLock.writeLock(ReadWriteLock.java:127)
at org.apache.jcs.auxiliary.disk.indexed.IndexedDiskCache.doUpdate(IndexedDiskCache.java:252)
at org.apache.jcs.auxiliary.disk.AbstractDiskCache$MyCacheListener.handlePut(AbstractDiskCache.java:417)
at org.apache.jcs.engine.CacheEventQueue$PutEvent.doRun(CacheEventQueue.java:440)
at org.apache.jcs.engine.CacheEventQueue$AbstractCacheEvent.run(CacheEventQueue.java:358)
at org.apache.jcs.engine.CacheEventQueue$QProcessor.run(CacheEventQueue.java:327)
22.06.2004 10:21:55 org.apache.jcs.engine.CacheEventQueue$QProcessor run
INFO: QProcessor exiting for listenerId=118, cacheName=main
22.06.2004 10:21:55 org.apache.jcs.auxiliary.disk.indexed.IndexedDiskCache optimizeFile
INFO: Optomizing file keyHash.size()=0
22.06.2004 10:21:55 org.apache.jcs.auxiliary.disk.indexed.IndexedDiskCache doDispose
WARNUNG: Closing files, base filename: main
22.06.2004 10:21:55 org.apache.jcs.engine.control.CompositeCache dispose
WARNUNG: Called close for main
22.06.2004 10:21:55 org.apache.jcs.engine.CacheEventQueue$QProcessor run
INFO: QProcessor exiting for listenerId=118, cacheName=groupIdCache
22.06.2004 10:21:55 org.apache.jcs.engine.CacheEventQueue destroy
INFO: Cache event queue destroyed: listenerId=118, cacheName=groupIdCache
22.06.2004 10:21:55 org.apache.jcs.auxiliary.disk.indexed.IndexedDiskCache optimizeFile
INFO: Optomizing file keyHash.size()=0
22.06.2004 10:21:55 org.apache.jcs.auxiliary.disk.indexed.IndexedDiskCache doDispose
WARNUNG: Closing files, base filename: groupIdCache
22.06.2004 10:21:55 org.apache.jcs.engine.control.CompositeCache dispose
WARNUNG: Called close for groupIdCache
Total time: 0 minutes 18 seconds, Site size: 321.666 Site pages: 36
Warning: C:\develop\workspace\de.escnet.net4j.docs\src\skins\common\images not found.
Warning: C:\develop\workspace\de.escnet.net4j.docs\src\skins\tigris-style\images not found.
Copying 6 files to C:\develop\workspace\de.escnet.net4j.docs\build\site\skin
Copied 3 empty directories to 2 empty directories under C:\develop\workspace\de.escnet.net4j.docs\build\site\skin
Copying 8 files to C:\develop\workspace\de.escnet.net4j.docs\build\site\skin
Warning: C:\develop\workspace\de.escnet.net4j.docs\src\skins\common not found.
Warning: C:\develop\workspace\de.escnet.net4j.docs\src\skins\tigris-style not found.
Static site will be generated at:
C:\develop\workspace\de.escnet.net4j.docs\build\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:
C:\develop\workspace\de.escnet.net4j.docs\build\brokenlinks.xml
for any broken links in the generated site.
------------------------------
Static site was successfully generated at:
C:\develop\workspace\de.escnet.net4j.docs\build\site
------------------------------
BUILD SUCCESSFUL
Total time: 25 seconds
thanks
/eike
commenting and voting for Jira issues (Was: can i use the trunk?)
Posted by David Crossley <cr...@apache.org>.
Eike Stepper wrote:
> David Crossley wrote:
> > The values are set in skinconf.xml and applied by
> > src/core/context/skins/common/xslt/fo/document2fo.xsl
> > However it appears that these values are being ignored.
> >
> > http://issues.cocoondev.org/jira//secure/ViewIssue.jspa?key=FOR-138
>
> i've tried to vote for it, but the issue tracker keeps saying:
> "If you were logged in you would be able to see more functions."
Yes that is correct. If you want to modify Jira issues
then you need to "Signup" for a user account.
--David
Re: can i use the trunk?
Posted by Eike Stepper <st...@esc-net.de>.
"David Crossley" <cr...@apache.org> schrieb im Newsbeitrag news:1087822108.1555.2429.camel@ighp...
> Eike Stepper wrote:
> > i'm quite new to forrest and had just managed to build
> > a first small site with the forrest-0.5.1-bin release. now
> > i have tried to use the trunk version of forrest from svn.
>
> This can certainly be done. Have you followed the
> document called upgrading_06.html ?
no, i will look for it and come back if there are open questions...
> > it appears that not all of the raw files are copied to the
> > build folder, but only the ones directly referenced by some
> > xdocs.
>
> There should be no copying at all. If a few things are
> still being copied, then they are glitches that we are
> gradually fixing in the build process.
i suppose that the above mentioned doc will make it clear.
> > ... that is fatal for my javadocs.
>
> Not sure what you mean by that.
i've set up the forrest.properties with:
project.raw-content-dir=${project.content-dir}/content/raw
project.xdocs-dir=${project.content-dir}/content/xdocs
and my build script generates the javadocs to
${project.content-dir}/content/raw/docs/api.
when i run "forrest" only the directly referenced htmls are copied
to build/site/...
> > is there an undocumented switch?
> >
> > btw. is there a place where i can tweak the generated pdfs?
> > (their appearance is rather evil, no margins...)
>
> Better to use separate emails for separate topics.
next time ;-)
> Yes the PDF margins definitely need some work.
> Do you want to help?
i'd like to but i'm totally busy with two other open source projects:
http://net4j.berlios.de and http://developer.berlios.de/projects/cdo
> The values are set in skinconf.xml and applied by
> src/core/context/skins/common/xslt/fo/document2fo.xsl
> However it appears that these values are being ignored.
>
> http://issues.cocoondev.org/jira//secure/ViewIssue.jspa?key=FOR-138
i've tried to vote for it, but the issue tracker keeps saying:
"If you were logged in you would be able to see more functions."
ciao
/eike
Re: can i use the trunk?
Posted by David Crossley <cr...@apache.org>.
Eike Stepper wrote:
> i'm quite new to forrest and had just managed to build
> a first small site with the forrest-0.5.1-bin release. now
> i have tried to use the trunk version of forrest from svn.
This can certainly be done. Have you followed the
document called upgrading_06.html ?
> it appears that not all of the raw files are copied to the
> build folder, but only the ones directly referenced by some
> xdocs.
There should be no copying at all. If a few things are
still being copied, then they are glitches that we are
gradually fixing in the build process.
> ... that is fatal for my javadocs.
Not sure what you mean by that.
> is there an undocumented switch?
>
> btw. is there a place where i can tweak the generated pdfs?
> (their appearance is rather evil, no margins...)
Better to use separate emails for separate topics.
Yes the PDF margins definitely need some work.
Do you want to help?
The values are set in skinconf.xml and applied by
src/core/context/skins/common/xslt/fo/document2fo.xsl
However it appears that these values are being ignored.
http://issues.cocoondev.org/jira//secure/ViewIssue.jspa?key=FOR-138
--
David Crossley