You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by "Adam R. B. Jack" <aj...@trysybase.com> on 2003/12/09 19:57:17 UTC

Troubleshooting help w/ forrest, please...

Ok, I now know I have this:

    Forrest Site Builder  0.6-dev  $Date: 2003/12/04 22:08:19

but I still get this, which seems to work for some, some times.

X [0]                       images/gump-logo.png BROKEN:
java.lang.NullPointerException

[Full log below.]

How can I get more information from this? Can I get a stack trace to post?

Also, with broken links, is there a way to know where it is referenced from?
When I move pages around (and create sub-directories) I cause broken links,
but they are hard to track down. Anything available to help me here?

[P.S. I looked for a troubleshooting section on the forrest site, but didn't
find one.]

regards

Adam
----------------------------------------------------------------------------
------------------



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


Buildfile: F:\data\OSS\forrest\forrest.build.xml

init-props:
Loading project specific properties from
F:\data\OSS\jakarta-gump\forrest.properties
Reading filters from
F:\data\OSS\jakarta-gump\build\tmp\projfilters.properties

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

init-skinprops:
Reading filters from
F:\data\OSS\jakarta-gump\build\tmp\skinfilters.properties

validate-xdocs:
19 file(s) have been successfully validated.
...validated xdocs

validate-sitemap:
...validated sitemap

validate-skinchoice:
...validated existence of skin 'forrest-site'

bare-context:
____________________________________
Using skin forrest-site
____________________________________
Copying 16 files to F:\data\OSS\jakarta-gump\build\webapp
Replacing: @skin@ -> forrest-site
Replacing: @menu-scheme@ -> tab_attributes
Replacing: @bugtracking-url@ ->
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=
Replacing: @i18n@ -> false
Replacing: @forrest.home@ -> F:\data\OSS\forrest
Replacing: @forrest.home@ -> F:\data\OSS\forrest
Replacing: @skin@ -> forrest-site
Replacing: @project.home@ -> F:\data\OSS\jakarta-gump
Replacing: @project.skinconf@ -> src/documentation/skinconf.xml
Replacing: @project.home@ -> F:\data\OSS\jakarta-gump
Replacing: @project.content-dir@ -> src/documentation
Replacing: @project.home@ -> F:\data\OSS\jakarta-gump
Replacing: @project.raw-content-dir@ -> src/documentation/content
Replacing: @project.home@ -> F:\data\OSS\jakarta-gump
Replacing: @project.xdocs-dir@ -> src/documentation/content/xdocs
Replacing: @project.home@ -> F:\data\OSS\jakarta-gump
Replacing: @project.translations-dir@ -> src/documentation/translations
Replacing: @project.home@ -> F:\data\OSS\jakarta-gump
Replacing: @project.stylesheets-dir@ ->
src/documentation/resources/stylesheets
Replacing: @project.home@ -> F:\data\OSS\jakarta-gump
Replacing: @project.images-dir@ -> src/documentation/resources/images
Replacing: @project.home@ -> F:\data\OSS\jakarta-gump
Replacing: @project.skins-dir@ -> src/documentation/skins
Replacing: @forrest.home@ -> F:\data\OSS\forrest
Replacing: @local-catalog@ ->
F:\data\OSS\jakarta-gump\src\documentation\resources\schema\catalog.xcat
Replacing: @catalog-verbosity@ -> 1

copy-skinconf:
Copying 1 file to F:\data\OSS\jakarta-gump\build\webapp

init-props:
Loading project specific properties from
F:\data\OSS\jakarta-gump\forrest.properties
Reading filters from
F:\data\OSS\jakarta-gump\build\tmp\projfilters.properties

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

init-skinprops:
Reading filters from
F:\data\OSS\jakarta-gump\build\tmp\skinfilters.properties
---------------------------------
Webapp generated in F:\data\OSS\jakarta-gump\build\webapp

To run in Tomcat, add this to the config file (usu. server.xml):

&lt;Context path='/Jakarta Gump'
            docBase='F:\data\OSS\jakarta-gump\build\webapp'
            reloadable='true'/&gt;

If using JDK 1.4 or above, make sure to set the Java environment variable
-Djava.endorsed.dirs=F:\data\OSS\forrest\lib\endorsed
Eg, in the TOMCAT_OPTS (3.3.x) or CATALINA_OPTS (4.x) env variable.
---------------------------------

site:
Deleting directory F:\data\OSS\jakarta-gump\build\tmp\cocoon-work
Created dir: F:\data\OSS\jakarta-gump\build\tmp\cocoon-work
Warning: F:\data\OSS\jakarta-gump\build\webapp\resources not found.
Copying 1 file to F:\data\OSS\jakarta-gump\build\site
Copying 37 files to F:\data\OSS\jakarta-gump\build\site\skin\images
Warning: F:\data\OSS\jakarta-gump\src\documentation\skins\common\images not
found.
Warning:
F:\data\OSS\jakarta-gump\src\documentation\skins\forrest-site\images not
found.
Copying 7 files to F:\data\OSS\jakarta-gump\build\site\skin
Warning: F:\data\OSS\jakarta-gump\src\documentation\skins\common not found.
Warning: F:\data\OSS\jakarta-gump\src\documentation\skins\forrest-site not
found.

Static site will be generated at:
F:\data\OSS\jakarta-gump\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:
F:\data\OSS\jakarta-gump\build\brokenlinks.xml
for any broken links in the generated site.

------------------------------------------------------------------------ 
cocoon 2.1.2-dev
Copyright (c) 1999-2003 Apache Software Foundation. All rights reserved.
------------------------------------------------------------------------ 
* [0/0]      2.313s 766b    favicon.ico
* [29/0]     11.026s 21.1Kb  index.html
* [0/0]      0.34s  1.1Kb   skin/images/vcss.png
* [32/0]     2.093s 18.9Kb  why.html
* [0/0]      0.07s  70b     skin/images/tabSel-left.gif
* [0/0]      0.061s 55b     skin/images/chapter.gif
* [0/0]      0.06s  1.8Kb   images/built-with-forrest-button.png
* [0/0]      0.24s  2.8Kb   skin/page.css
* [25/0]     2.133s 11.7Kb  traditional/index.html
* [36/0]     1.412s 16.3Kb  metadata/index.html
* [34/0]     3.776s 39.6Kb  metadata/project.html
* [22/0]     1.261s 16.4Kb  python/usage.html
* [0/0]      0.04s  2.8Kb   skin/images/valid-html401.png
* [0/0]      0.331s 8.5Kb   skin/breadcrumbs.js
* [30/0]     2.063s 13.8Kb  metadata/practices.html
* [27/0]     1.352s 15.3Kb  metadata/repository.html
* [0/0]      0.1s   176b    skin/images/menu-left.gif
* [0/0]      0.06s  176b    skin/images/menu-right.gif
* [0/0]      0.04s  70b     skin/images/tab-left.gif
* [0/0]      0.04s  54b     skin/images/label.gif
* [0/0]      0.06s  52b     skin/images/page.gif
* [22/0]     1.122s 13.5Kb  traditional/usage.html
* [29/0]     2.293s 17.9Kb  metadata/module.html
* [0/0]      0.04s  766b    /favicon.ico
* [0/0]      0.06s  70b     skin/images/tab-right.gif
* [24/0]     1.252s 16.2Kb  status.html
* [27/0]     1.412s 18.3Kb  faq.html
* [0/0]      0.12s  457b    skin/images/pdfdoc.gif
* [27/0]     2.294s 17.6Kb  metadata/ant.html
* [0/0]      0.04s  16.8Kb  images/apache-jakarta.png
* [0/0]      0.1s   60b     skin/images/current.gif
* [32/0]     1.081s 16.4Kb  nagged.html
* [24/0]     1.072s 16.5Kb  gettingstarted.html
X [0]                       /site/getinvolved.html BROKEN:
F:\data\OSS\jakarta-gump\src\documentation\content\xdocs\site\getinvolved.xm
l (The system cannot find the path specified)
* [30/0]     2.113s 14.8Kb  metadata/profile.html
* [0/0]      7.982s 14.6Kb  faq.pdf
* [26/0]     0.931s 12.2Kb  python/index.html
* [0/0]      0.12s  65.6Kb  graphics/view.jpg
* [0/0]      0.07s  70b     skin/images/tabSel-right.gif
* [0/0]      0.03s  43b     skin/images/spacer.gif
* [32/0]     1.382s 25.5Kb  metadata/workspace.html
* [0/0]      0.101s 55b     skin/images/chapter_open.gif
X [0]                       images/gump-logo.png BROKEN:
java.lang.NullPointerException
Total time: 1 minutes 3 seconds

BUILD FAILED
F:\data\OSS\forrest\forrest.build.xml:500: Java returned: 1

Total time: 1 minute 32 seconds

--
Experience the Unwired Enterprise:
http://www.sybase.com/unwiredenterprise
Try Sybase: http://www.try.sybase.com


Re: broken skinconfig breadcrumb trail

Posted by David Crossley <cr...@indexgeo.com.au>.
David Crossley wrote:
> Adam R. B. Jack wrote:
> > ...Now my problem is the trail.
>
> Yes i see this issue at various other sites, e.g.
> http://xml.apache.org/ ... although their problem seems
> different to yours.
> 
> One cause could be that the JavaScript files were not
> published to your website at skins/breadcrumbs*.js

I meant skin/breadcrumbs*.js

> Another cause could be incorrect configuration in the
> skinconf.xml file.
> 
> Of course it could be a bug. I notice that you have whitespace
> in the second label. Could that be it? Patch appreciated.
> 
> --David

> > Jakarta > Jakarta Gump @skinconfig.trail.link1.name@ >
> > @skinconfig.trail.link2.name@ > @skinconfig.trail.link3.name@ > gump > new
> > 
> > http://jakarta.apache.org/gump/new/index.html

Oooh, i see that a similar problem is recently occurring at
the Forrest website. I have no idea why.

--David


broken skinconfig breadcrumb trail (Was: Troubleshooting help w/ forrest, please...)

Posted by David Crossley <cr...@indexgeo.com.au>.
Adam R. B. Jack wrote:
> I'm still curious how to troubleshoot, but I've temporarily
> rolled back the SVG. Now my problem is the trail.
> 
> Anybody able to help me get past this?

Please ask separate questions under separate Subjects.
That enables others to follow the issue more easily.

Yes i see this issue at various other sites, e.g.
http://xml.apache.org/ ... although their problem seems
different to yours.

One cause could be that the JavaScript files were not
published to your website at skins/breadcrumbs*.js

Another cause could be incorrect configuration in the
skinconf.xml file.

Of course it could be a bug. I notice that you have whitespace
in the second label. Could that be it? Patch appreciated.

--David

> See:
> 
> Jakarta > Jakarta Gump @skinconfig.trail.link1.name@ >
> @skinconfig.trail.link2.name@ > @skinconfig.trail.link3.name@ > gump > new
> 
> http://jakarta.apache.org/gump/new/index.html
> 
> regards,
> 
> Adam



Re: Troubleshooting help w/ forrest, please...

Posted by "Adam R. B. Jack" <aj...@trysybase.com>.
I'm still curious how to troubleshoot, but I've temporarily rolled back the
SVG. Now my problem is the trail.

Anybody able to help me get past this?

See:

Jakarta > Jakarta Gump @skinconfig.trail.link1.name@ >
@skinconfig.trail.link2.name@ > @skinconfig.trail.link3.name@ > gump > new

http://jakarta.apache.org/gump/new/index.html

regards,

Adam
----- Original Message ----- 
From: "Adam R. B. Jack" <aj...@trysybase.com>
To: <fo...@xml.apache.org>
Sent: Tuesday, December 09, 2003 11:57 AM
Subject: Troubleshooting help w/ forrest, please...


> Ok, I now know I have this:
>
>     Forrest Site Builder  0.6-dev  $Date: 2003/12/04 22:08:19
>
> but I still get this, which seems to work for some, some times.
>
> X [0]                       images/gump-logo.png BROKEN:
> java.lang.NullPointerException
>
> [Full log below.]
>
> How can I get more information from this? Can I get a stack trace to post?
>
> Also, with broken links, is there a way to know where it is referenced
from?
> When I move pages around (and create sub-directories) I cause broken
links,
> but they are hard to track down. Anything available to help me here?
>
> [P.S. I looked for a troubleshooting section on the forrest site, but
didn't
> find one.]
>
> regards
>
> Adam
> --------------------------------------------------------------------------
--
> ------------------
>
>
>
> Apache Forrest.  Run 'forrest -projecthelp' to list options
>
>
> Buildfile: F:\data\OSS\forrest\forrest.build.xml
>
> init-props:
> Loading project specific properties from
> F:\data\OSS\jakarta-gump\forrest.properties
> Reading filters from
> F:\data\OSS\jakarta-gump\build\tmp\projfilters.properties
>
> echo-settings:
>       ------------------------------------------------
>       | Forrest template run.
>       | Running from ${forrest.home} = F:\data\OSS\forrest
>       | Working on   ${project.home} = F:\data\OSS\jakarta-gump
>       ------------------------------------------------
>       | //where to put the result
>       | project.site-dir    = F:\data\OSS\jakarta-gump\build\site
>       | //uri to start crawling/generation process
>       | project.start-uri   = index.html
>       | //cocoon.xconf location
>       | project.configfile  =
> F:\data\OSS\jakarta-gump\build\webapp/WEB-INF/cli.xconf
>       | //logkit.xconf location
>       | project.logkitfile  =
> F:\data\OSS\jakarta-gump\build\webapp/WEB-INF/logkit.xconf
>       | //temp dir to throw stuff in (i.e. work and ctxt)
>       | project.temp-dir    = F:\data\OSS\jakarta-gump\build\tmp
>       | //temp working directory for generation process
>       | project.cocoon-work-dir    =
> F:\data\OSS\jakarta-gump\build\tmp\cocoon-work
>       | //temp context directory for generation process
>       | project.webapp    = F:\data\OSS\jakarta-gump\build\webapp
>       | //debuglevel for logging (DEBUG, INFO, WARN, ERROR, FATAL_ERROR)
>       | project.debuglevel  = ERROR
>       | //file for list of broken links
>       | project.brokenlinkfile =
> F:\data\OSS\jakarta-gump\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        = forrest-site
>       | //where your documentation xml is
>       | project.content-dir = F:\data\OSS\jakarta-gump\src\documentation
>       ------------------------------------------------
>
> init-skinprops:
> Reading filters from
> F:\data\OSS\jakarta-gump\build\tmp\skinfilters.properties
>
> validate-xdocs:
> 19 file(s) have been successfully validated.
> ...validated xdocs
>
> validate-sitemap:
> ...validated sitemap
>
> validate-skinchoice:
> ...validated existence of skin 'forrest-site'
>
> bare-context:
> ____________________________________
> Using skin forrest-site
> ____________________________________
> Copying 16 files to F:\data\OSS\jakarta-gump\build\webapp
> Replacing: @skin@ -> forrest-site
> Replacing: @menu-scheme@ -> tab_attributes
> Replacing: @bugtracking-url@ ->
> http://nagoya.apache.org/bugzilla/show_bug.cgi?id=
> Replacing: @i18n@ -> false
> Replacing: @forrest.home@ -> F:\data\OSS\forrest
> Replacing: @forrest.home@ -> F:\data\OSS\forrest
> Replacing: @skin@ -> forrest-site
> Replacing: @project.home@ -> F:\data\OSS\jakarta-gump
> Replacing: @project.skinconf@ -> src/documentation/skinconf.xml
> Replacing: @project.home@ -> F:\data\OSS\jakarta-gump
> Replacing: @project.content-dir@ -> src/documentation
> Replacing: @project.home@ -> F:\data\OSS\jakarta-gump
> Replacing: @project.raw-content-dir@ -> src/documentation/content
> Replacing: @project.home@ -> F:\data\OSS\jakarta-gump
> Replacing: @project.xdocs-dir@ -> src/documentation/content/xdocs
> Replacing: @project.home@ -> F:\data\OSS\jakarta-gump
> Replacing: @project.translations-dir@ -> src/documentation/translations
> Replacing: @project.home@ -> F:\data\OSS\jakarta-gump
> Replacing: @project.stylesheets-dir@ ->
> src/documentation/resources/stylesheets
> Replacing: @project.home@ -> F:\data\OSS\jakarta-gump
> Replacing: @project.images-dir@ -> src/documentation/resources/images
> Replacing: @project.home@ -> F:\data\OSS\jakarta-gump
> Replacing: @project.skins-dir@ -> src/documentation/skins
> Replacing: @forrest.home@ -> F:\data\OSS\forrest
> Replacing: @local-catalog@ ->
> F:\data\OSS\jakarta-gump\src\documentation\resources\schema\catalog.xcat
> Replacing: @catalog-verbosity@ -> 1
>
> copy-skinconf:
> Copying 1 file to F:\data\OSS\jakarta-gump\build\webapp
>
> init-props:
> Loading project specific properties from
> F:\data\OSS\jakarta-gump\forrest.properties
> Reading filters from
> F:\data\OSS\jakarta-gump\build\tmp\projfilters.properties
>
> echo-settings:
>       ------------------------------------------------
>       | Forrest template run.
>       | Running from ${forrest.home} = F:\data\OSS\forrest
>       | Working on   ${project.home} = F:\data\OSS\jakarta-gump
>       ------------------------------------------------
>       | //where to put the result
>       | project.site-dir    = F:\data\OSS\jakarta-gump\build\site
>       | //uri to start crawling/generation process
>       | project.start-uri   = index.html
>       | //cocoon.xconf location
>       | project.configfile  =
> F:\data\OSS\jakarta-gump\build\webapp/WEB-INF/cli.xconf
>       | //logkit.xconf location
>       | project.logkitfile  =
> F:\data\OSS\jakarta-gump\build\webapp/WEB-INF/logkit.xconf
>       | //temp dir to throw stuff in (i.e. work and ctxt)
>       | project.temp-dir    = F:\data\OSS\jakarta-gump\build\tmp
>       | //temp working directory for generation process
>       | project.cocoon-work-dir    =
> F:\data\OSS\jakarta-gump\build\tmp\cocoon-work
>       | //temp context directory for generation process
>       | project.webapp    = F:\data\OSS\jakarta-gump\build\webapp
>       | //debuglevel for logging (DEBUG, INFO, WARN, ERROR, FATAL_ERROR)
>       | project.debuglevel  = ERROR
>       | //file for list of broken links
>       | project.brokenlinkfile =
> F:\data\OSS\jakarta-gump\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        = forrest-site
>       | //where your documentation xml is
>       | project.content-dir = F:\data\OSS\jakarta-gump\src\documentation
>       ------------------------------------------------
>
> init-skinprops:
> Reading filters from
> F:\data\OSS\jakarta-gump\build\tmp\skinfilters.properties
> ---------------------------------
> Webapp generated in F:\data\OSS\jakarta-gump\build\webapp
>
> To run in Tomcat, add this to the config file (usu. server.xml):
>
> &lt;Context path='/Jakarta Gump'
>             docBase='F:\data\OSS\jakarta-gump\build\webapp'
>             reloadable='true'/&gt;
>
> If using JDK 1.4 or above, make sure to set the Java environment variable
> -Djava.endorsed.dirs=F:\data\OSS\forrest\lib\endorsed
> Eg, in the TOMCAT_OPTS (3.3.x) or CATALINA_OPTS (4.x) env variable.
> ---------------------------------
>
> site:
> Deleting directory F:\data\OSS\jakarta-gump\build\tmp\cocoon-work
> Created dir: F:\data\OSS\jakarta-gump\build\tmp\cocoon-work
> Warning: F:\data\OSS\jakarta-gump\build\webapp\resources not found.
> Copying 1 file to F:\data\OSS\jakarta-gump\build\site
> Copying 37 files to F:\data\OSS\jakarta-gump\build\site\skin\images
> Warning: F:\data\OSS\jakarta-gump\src\documentation\skins\common\images
not
> found.
> Warning:
> F:\data\OSS\jakarta-gump\src\documentation\skins\forrest-site\images not
> found.
> Copying 7 files to F:\data\OSS\jakarta-gump\build\site\skin
> Warning: F:\data\OSS\jakarta-gump\src\documentation\skins\common not
found.
> Warning: F:\data\OSS\jakarta-gump\src\documentation\skins\forrest-site not
> found.
>
> Static site will be generated at:
> F:\data\OSS\jakarta-gump\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:
> F:\data\OSS\jakarta-gump\build\brokenlinks.xml
> for any broken links in the generated site.
>
> ------------------------------------------------------------------------ 
> cocoon 2.1.2-dev
> Copyright (c) 1999-2003 Apache Software Foundation. All rights reserved.
> ------------------------------------------------------------------------ 
> * [0/0]      2.313s 766b    favicon.ico
> * [29/0]     11.026s 21.1Kb  index.html
> * [0/0]      0.34s  1.1Kb   skin/images/vcss.png
> * [32/0]     2.093s 18.9Kb  why.html
> * [0/0]      0.07s  70b     skin/images/tabSel-left.gif
> * [0/0]      0.061s 55b     skin/images/chapter.gif
> * [0/0]      0.06s  1.8Kb   images/built-with-forrest-button.png
> * [0/0]      0.24s  2.8Kb   skin/page.css
> * [25/0]     2.133s 11.7Kb  traditional/index.html
> * [36/0]     1.412s 16.3Kb  metadata/index.html
> * [34/0]     3.776s 39.6Kb  metadata/project.html
> * [22/0]     1.261s 16.4Kb  python/usage.html
> * [0/0]      0.04s  2.8Kb   skin/images/valid-html401.png
> * [0/0]      0.331s 8.5Kb   skin/breadcrumbs.js
> * [30/0]     2.063s 13.8Kb  metadata/practices.html
> * [27/0]     1.352s 15.3Kb  metadata/repository.html
> * [0/0]      0.1s   176b    skin/images/menu-left.gif
> * [0/0]      0.06s  176b    skin/images/menu-right.gif
> * [0/0]      0.04s  70b     skin/images/tab-left.gif
> * [0/0]      0.04s  54b     skin/images/label.gif
> * [0/0]      0.06s  52b     skin/images/page.gif
> * [22/0]     1.122s 13.5Kb  traditional/usage.html
> * [29/0]     2.293s 17.9Kb  metadata/module.html
> * [0/0]      0.04s  766b    /favicon.ico
> * [0/0]      0.06s  70b     skin/images/tab-right.gif
> * [24/0]     1.252s 16.2Kb  status.html
> * [27/0]     1.412s 18.3Kb  faq.html
> * [0/0]      0.12s  457b    skin/images/pdfdoc.gif
> * [27/0]     2.294s 17.6Kb  metadata/ant.html
> * [0/0]      0.04s  16.8Kb  images/apache-jakarta.png
> * [0/0]      0.1s   60b     skin/images/current.gif
> * [32/0]     1.081s 16.4Kb  nagged.html
> * [24/0]     1.072s 16.5Kb  gettingstarted.html
> X [0]                       /site/getinvolved.html BROKEN:
>
F:\data\OSS\jakarta-gump\src\documentation\content\xdocs\site\getinvolved.xm
> l (The system cannot find the path specified)
> * [30/0]     2.113s 14.8Kb  metadata/profile.html
> * [0/0]      7.982s 14.6Kb  faq.pdf
> * [26/0]     0.931s 12.2Kb  python/index.html
> * [0/0]      0.12s  65.6Kb  graphics/view.jpg
> * [0/0]      0.07s  70b     skin/images/tabSel-right.gif
> * [0/0]      0.03s  43b     skin/images/spacer.gif
> * [32/0]     1.382s 25.5Kb  metadata/workspace.html
> * [0/0]      0.101s 55b     skin/images/chapter_open.gif
> X [0]                       images/gump-logo.png BROKEN:
> java.lang.NullPointerException
> Total time: 1 minutes 3 seconds
>
> BUILD FAILED
> F:\data\OSS\forrest\forrest.build.xml:500: Java returned: 1
>
> Total time: 1 minute 32 seconds
>
> --
> Experience the Unwired Enterprise:
> http://www.sybase.com/unwiredenterprise
> Try Sybase: http://www.try.sybase.com
>


Re: 0.6 release

Posted by Marshall Roch <ma...@exclupen.com>.
Dave Brondsema wrote:
> I'd like to get the new forrestbot into the next release.  All I have to do is
> write a local & ssh deployment implementation and then make sure the buildfiles
> for the ASF sites work.  And then of course move it from the scratchpad to main.
> 
> Now that there's documentation, those of you who are interested should start
> testing it to see if there's any bugs.

Please don't forget about the broken skin thing. I know it doesn't 
affect ASF sites, but as of last night's CVS, that bug is a showstopper 
for everyone using a custom skin.  You don't want to release software 
that's completely broken for everyone outside Apache.

--
Marshall Roch

Re: 0.6 release (was: Troubleshooting help w/ forrest, please...)

Posted by Dave Brondsema <da...@brondsema.net>.
Quoting Nicola Ken Barozzi <ni...@apache.org>:

> I'm back from my holidays now, and I'll try to wrap up all changes to 
> Forrest so that we can make a Christmas release :-)
> 

I'd like to get the new forrestbot into the next release.  All I have to do is
write a local & ssh deployment implementation and then make sure the buildfiles
for the ASF sites work.  And then of course move it from the scratchpad to main.

Now that there's documentation, those of you who are interested should start
testing it to see if there's any bugs.

-- 
Dave Brondsema 
dave@brondsema.net 
http://www.brondsema.net - personal 
http://www.splike.com - programming 
http://csx.calvin.edu - student org 

Re: Troubleshooting help w/ forrest, please...

Posted by Ross Gardler <rg...@wkwyw.net>.
Nicola Ken Barozzi wrote:
> I'm back from my holidays now, and I'll try to wrap up all changes to 
> Forrest so that we can make a Christmas release :-)

I'd also suggest a temporary fix for the problems deploying webapps. As 
you know I have a fix for this that works on Linux and on Windows with 
Cygwin. I can attach a patch to the relevant bug if you are interested 
in a temporary fix for the release, it's only a small change to the 
build file if I remember correctly.

I do have a fix that works on both platforms, it uses a separate config 
file and build for deployable webapps. However, it is not fully tested 
and is a little untidy at the moment and has some considerable changes 
in the build script. I'm not sure if I'm going to find the time to test 
and tidy it up before XMas. So it probably would not be a good idea to 
include it in the 0.6 release. However, I can upload a patch if you like.

Ross



Re: Troubleshooting help w/ forrest, please...

Posted by Nicola Ken Barozzi <ni...@apache.org>.
I have just fixed the errors that were on the gump site sources in CVS.

Basically the images were in resources/images and it didn't find them, 
so moving them to xdocs/images. Probably it should have worked but I 
just moved the files without checking Forrest much.

Then site.xml was not being used as intended, as it was being used as a 
bug book.xml (it also have a book DTD reference in it), and I fixed this 
also.

I'm back from my holidays now, and I'll try to wrap up all changes to 
Forrest so that we can make a Christmas release :-)

-- 
Nicola Ken Barozzi                   nicolaken@apache.org
             - verba volant, scripta manent -
    (discussions get forgotten, just code remains)
---------------------------------------------------------------------


Re: Troubleshooting help w/ forrest, please...

Posted by David Crossley <cr...@indexgeo.com.au>.
Adam R. B. Jack wrote:
> Ok, I now know I have this:
> 
>     Forrest Site Builder  0.6-dev  $Date: 2003/12/04 22:08:19
> 
> but I still get this, which seems to work for some, some times.
>
> X [0]                       images/gump-logo.png BROKEN:
> java.lang.NullPointerException
> 
> [Full log below.]

You say that it works for some of the people some of the time.
Is it perhaps an issue with PDF production?
http://xml.apache.org/forrest/faq.html#pdf_images

> How can I get more information from this? Can I get a stack trace to post?

Did you see the FAQ about logfiles? It is a bit obscure:
http://xml.apache.org/forrest/faq.html#checked_out_now_what
Do the logfiles help you?

> Also, with broken links, is there a way to know where it is referenced from?

I heard some talk on this list, that future Cocoon CLI might be able to.

In the meantime ... UNIX find and grep are your friend.

> When I move pages around (and create sub-directories) I cause broken links,
> but they are hard to track down. Anything available to help me here?

Are you using a "site.xml" to define your doc space and
using "site:blah" hrefs? If so then it should be easy to move
stuff around.

> [P.S. I looked for a troubleshooting section on the forrest site,
> but didn'tfind one.]

We generally try to put that sort of stuff into the FAQ. Any patches
to that doc are welcome. I made one from your recent comments about
Forrest version number, but would prefer that others contributed too.

--David