forrest-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Howard Lewis Ship <hls...@gmail.com>
Subject Re: Upgrade to 0.6: validation issues
Date Tue, 19 Oct 2004 11:24:46 GMT
Nope; even the forrest.bat tool isn't working:

C:\workspace\jakarta-hivemind>set
FORREST_HOME=C:\workspace\jakarta-hivemind\ext-package\apache-forrest-0.6\src\core

C:\workspace\jakarta-hivemind>set PATH=%FORREST_HOME%/bin;%PATH%

C:\workspace\jakarta-hivemind>forrest

Apache Forrest.  Run 'forrest -projecthelp' to list options


Buildfile: C:\workspace\jakarta-hivemind\ext-package\apache-forrest-0.6\src\core\forrest.build.xml

init-props:
Loading project specific properties from
C:\workspace\jakarta-hivemind\forrest.properties
Loading user specific properties from C:\Documents and
Settings\Howard\forrest.properties
Loading default properties from
C:\workspace\jakarta-hivemind\ext-package\apache-forrest-0.6\src\core\context\default-forrest.properties

echo-settings:
      ------------------------------------------------
      | Forrest template run.
      | Running from ${forrest.home} =
C:\workspace\jakarta-hivemind\ext-package\apache-forrest-0.6\src\core
      | Working on   ${project.home} = C:\workspace\jakarta-hivemind
      ------------------------------------------------
      | //where to put the result
      | project.site-dir    = C:\workspace\jakarta-hivemind/target/docs
      | //uri to start crawling/generation process
      | project.start-uri   = linkmap.html
      | //cocoon cli.xconf location
      | project.configfile  =
C:\workspace\jakarta-hivemind\ext-package\apache-forrest-0.6\src\core/context/WEB-INF/cli.xconf
      | //logkit.xconf location
      | project.logkitfile  =
C:\workspace\jakarta-hivemind\ext-package\apache-forrest-0.6\src\core/context/WEB-INF/logkit.xconf
      | //temp dir to throw stuff in (i.e. work and ctxt)
      | project.temp-dir    = target/forrest
      | //temp working directory for generation process
      | project.cocoon-work-dir    =
C:\workspace\jakarta-hivemind\target\forrest\cocoon-work
      | //temp context directory for generation process
      | project.webapp    = C:\workspace\jakarta-hivemind\target\forrest\webapp
      | //debuglevel for logging (DEBUG, INFO, WARN, ERROR, FATAL_ERROR)
      | project.debuglevel  = DEBUG
      | //file for list of broken links
      | project.brokenlinkfile =
C:\workspace\jakarta-hivemind\target\forrest\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        = pelt
      | //where your documentation xml is
      | project.content-dir =
C:\workspace\jakarta-hivemind\target\forrest-composite
      ------------------------------------------------

validate-xdocs:
45 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 'pelt'

site:
Deleting directory C:\workspace\jakarta-hivemind\target\forrest\cocoon-work
Created dir: C:\workspace\jakarta-hivemind\target\forrest\cocoon-work

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:\workspace\jakarta-hivemind\target\forrest\webapp\resources
not found.
Copying 1 file to C:\workspace\jakarta-hivemind\target\docs
Copying main skin images to site ...
Copying 21 files to C:\workspace\jakarta-hivemind\target\docs\skin\images
Copying 13 files to C:\workspace\jakarta-hivemind\target\docs\skin\images
Copying project skin images to site ...
Warning: C:\workspace\jakarta-hivemind\target\forrest-composite\skins\common\images
not found.
Warning: C:\workspace\jakarta-hivemind\target\forrest-composite\skins\pelt\images
not found.
Copying main skin css and js files to site ...
Copying 8 files to C:\workspace\jakarta-hivemind\target\docs\skin
Copying 6 files to C:\workspace\jakarta-hivemind\target\docs\skin
Copying project skin css and js files to site ...
Warning: C:\workspace\jakarta-hivemind\target\forrest-composite\skins\common
not found.
Warning: C:\workspace\jakarta-hivemind\target\forrest-composite\skins\pelt
not found.
Finished copying the non-generated resources.
Now Cocoon will generate the rest ...

Static site will be generated at:
C:\workspace\jakarta-hivemind/target/docs

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:\workspace\jakarta-hivemind\target\forrest\brokenlinks.xml
for any broken links in the generated site.
------------------------------------------------------------------------
cocoon 2.2.0-dev
Copyright (c) 1999-2004 Apache Software Foundation. All rights reserved.
------------------------------------------------------------------------
Cannot find CatalogManager.properties
X [0]                                     linkmap.html  BROKEN:
C:\workspace\jakarta-hivemind\ext-package\apache-forrest-0.6\src\core\context\target\forrest\build-info.xml
(Th
e system cannot find the path specified)
Total time: 0 minutes 13 seconds,  Site size: 0 Site pages: 0

BUILD FAILED
C:\workspace\jakarta-hivemind\ext-package\apache-forrest-0.6\src\core\targets\site.xml:43:
Java returned: 1

Total time: 33 seconds

C:\workspace\jakarta-hivemind>



On Mon, 18 Oct 2004 20:21:46 -0400, Dave Brondsema <dave@brondsema.net> wrote:
> Howard Lewis Ship wrote:
> > I tried the antproxy approach first, but the validation didn't work.
> > I'll revert back to that version and copy the output:
> >
> 
> Can you upgrade to 0.6 and run forrest manually succesfully?  Let's
> seperate issues of the 0.5->0.6 upgrade and using Ant <import> to run
> forrest.
> 
> --
> Dave Brondsema : dave@brondsema.net
> http://www.splike.com : programming
> http://csx.calvin.edu : student org
> http://www.brondsema.net : personal
> 
> 
> 


-- 
Howard M. Lewis Ship
Independent J2EE / Open-Source Java Consultant
Creator, Jakarta Tapestry
Creator, Jakarta HiveMind
http://howardlewisship.com

Mime
View raw message