You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@forrest.apache.org by Howard Lewis Ship <hl...@gmail.com> on 2004/10/17 17:27:13 UTC
Upgrade to 0.6: validation issues
I'm trying to upgrade to forrest 0.6.
First off; I had to change all my v1.2 DTD to v1.3, i.e.
<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.2//EN"
to
<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN"
I would have through Forrest 0.6 would have been gracious enough to
support v1.2? Perhaps it is related to my second problem:
Doesn't seem to be recognizing/using local catalogs and DTDs. Thus I
have to set my system identifier to
"http://xml.apache.org/forrest/dtd/document-v13.dtd"
for validation to work ... and validation is slow!
Here's how I run forrest:
<property name="forrest-package-dir"
value="${external.package.dir}/apache-forrest-0.6"/>
<property name="forrest.home" location="${forrest-package-dir}/src/core"/>
<import file="${forrest.home}/forrest.build.xml"/>
<target name="run-forrest" description="Runs Forrest to generate
final site documentation.">
<announce message="Invoking Forrest ..."/>
<antcall target="site.site"/>
</target>
Here's what it looks like at runtime:
bash-2.05b$ ant fast-site
Buildfile: build.xml
copy-documentation-to-composite:
fast-site:
copy-documentation-to-composite:
copy-documentation-to-composite:
copy-documentation-to-composite:
run-forrest:
[echo]
[echo]
[echo] *** Invoking Forrest ...
[echo]
init-props:
[echo] Loading project specific properties from
C:\workspace\jakarta-hivemind\forrest.properties
[echo] Loading user specific properties from C:\Documents and
Settings\Howard\forrest.properties
[echo] Loading default properties from
C:\workspace\jakarta-hivemind\ext-package\apache-forrest-0.6\src\core\context\default-forrest.properties
echo-settings:
[echo] ------------------------------------------------
[echo] | Forrest template run.
[echo] | Running from ${forrest.home} =
C:\workspace\jakarta-hivemind\ext-package\apache-forrest-0.6\src\core
[echo] | Working on ${project.home} = C:\workspace\jakarta-hivemind
[echo] ------------------------------------------------
[echo] | //where to put the result
[echo] | project.site-dir =
C:\workspace\jakarta-hivemind/target/docs
[echo] | //uri to start crawling/generation process
[echo] | project.start-uri = linkmap.html
[echo] | //cocoon cli.xconf location
[echo] | project.configfile =
C:\workspace\jakarta-hivemind\ext-package\apache-forrest-0.6\src\core/context/WEB-INF/cli.xconf
[echo] | //logkit.xconf location
[echo] | project.logkitfile =
C:\workspace\jakarta-hivemind\ext-package\apache-forrest-0.6\src\core/context/WEB-INF/logkit.xconf
[echo] | //temp dir to throw stuff in (i.e. work and ctxt)
[echo] | project.temp-dir = target/forrest
[echo] | //temp working directory for generation process
[echo] | project.cocoon-work-dir =
C:\workspace\jakarta-hivemind\target\forrest\cocoon-work
[echo] | //temp context directory for generation process
[echo] | project.webapp =
C:\workspace\jakarta-hivemind\target\forrest\webapp
[echo] | //debuglevel for logging (DEBUG, INFO, WARN,
ERROR, FATAL_ERROR)
[echo] | project.debuglevel = DEBUG
[echo] | //file for list of broken links
[echo] | project.brokenlinkfile =
C:\workspace\jakarta-hivemind\target\forrest\brokenlinks.xml
[echo] | //check if you have tools.jar installed
[echo] | tools.jar.present = true
[echo] ------------------------------------------------
[echo] | The following properties could be removed from
future builds:
[echo] | //which skin to apply
[echo] | project.skin = pelt
[echo] | //where your documentation xml is
[echo] | project.content-dir =
C:\workspace\jakarta-hivemind\target\forrest-composite
[echo] ------------------------------------------------
check-skin:
fetch-skins-descriptors:
fetch-skin:
unpack-skins:
init-skins:
init:
-prepare-classpath:
check-contentdir:
examine-proj:
validation-props:
validate-xdocs:
Warning: catalogpath listing external catalogs will be ignored
--
Howard M. Lewis Ship
Independent J2EE / Open-Source Java Consultant
Creator, Jakarta Tapestry
Creator, Jakarta HiveMind
http://howardlewisship.com
Re: Issues upgrading from 0.5 to 0.6
Posted by Howard Lewis Ship <hl...@gmail.com>.
On 28 Oct 2004 13:24:40 +1000, David Crossley <cr...@apache.org> wrote:
> I am not with you here. What bugs in 0.6?
I had a long thread last week or so about my many travails trying to
upgrade from 0.5 to 0.6. The thread is titled "Upgrade to 0.6:
validation issues". I've also documented on my blog some of these
issues:
http://howardlewisship.com/blog/2004/10/upgraded-hivemind-to-forrest-06.html
I was able to resolve most of them, but one particularily nasty bug
resulted in the index.html in each directory being exactly the same.
With much thrashing, I made the changes shown in that diff to force
forrest/cocoon to generate the correct content in each index.html.
--
Howard M. Lewis Ship
Independent J2EE / Open-Source Java Consultant
Creator, Jakarta Tapestry
Creator, Jakarta HiveMind
http://howardlewisship.com
Re: Issues upgrading from 0.5 to 0.6
Posted by David Crossley <cr...@apache.org>.
Howard Lewis Ship wrote:
> I'm aware of what I should be doing and much of it used to work in Forrest 0.5.
>
> See the diffs:
>
> http://cvs.apache.org/viewcvs.cgi/jakarta-hivemind/src/documentation/content/xdocs/site.xml?r1=1.26%3Arelease-1-0&tr1=1.28&r2=text&tr2=1.28&diff_format=h
Hmmm, but this is what i was referring to below.
I wonder if you do need the href="hivemind-examples/"
part which you removed.
> I had to strip out a lot of stuff that makes sense to work around bugs in 0.6.
I am not with you here. What bugs in 0.6?
> I'm still finding more problems; for example when trying to build
> wholesite.xml, I get:
>
> [java] X [0] wholesite.html
> BROKEN: java.lang.RuntimeException:
> org.apache.cocoon.ResourceNotFoundException: Resource not found.: o
> rg.apache.excalibur.source.SourceNotFoundException:
> file:/C:/workspace/jakarta-hivemind/target/forrest-composite/content/xdocs/hivedocs/index.xml
> doesn't exist.
>
> Even though my cli.xconf contains:
>
> <exclude pattern="hivedocs/**"/>
> <exclude pattern="**/hivedocs/**"/>
> <exclude pattern="**/apidocs/**"/>
> <exclude pattern="**/clover/**"/>
We know that there are problems with whole-site aggregation
and someone already advised you to leave it out for now.
> I also just noticed that top-level, non-menu elements in my site.xml
> don't appear.
This sounds like it is related to the missing href attributes.
--David
> Example:
>
> <reference label="Reference">
> <services label="Services" href="services.html"/>
> <configurations label="Configurations" href="configurations.html"/>
> <hivedoc label="HiveDoc" href="hivedoc.html"/>
> <descriptor label="Module Descriptor" href="descriptor.html"/>
> <rules label="Contribution Processing Rules" href="rules.html"/>
> <dependencies label="Dependencies" href="dependencies.html"/>
> </reference>
>
> <changes label="Change Log" href="changes.html"/>
> <todo label="TODO" href="todo.html"/>
>
> <mailinglists label="Mailing Lists"
> href="http://jakarta.apache.org/site/mail2.html#HiveMind"/>
>
> <downloads href="downloads.html" label="Downloads"/>
> <bugs href="http://issues.apache.org/jira/secure/BrowseProject.jspa?id=10500"
> label="Bugs"/>
>
> <cvs href="cvs.html" label="CVS Access"/>
>
> <tutorials label="Tutorials and Information">
>
> The "Reference" and "Tutorials and Information" menus appear, but none
> of the others do.
>
>
>
> On 27 Oct 2004 12:46:05 +1000, David Crossley <cr...@apache.org> wrote:
> > Howard Lewis Ship wrote:
> > > I eventually did get the HiveMind site building properly, but it took
> > > a LOT of effort.
> >
> > Phew. Very glad to see that you got there, and that
> > we could help in some places. Your situation was extra
> > difficult due to the integration of Forrest into your
> > build system. That should be possible, so we have some
> > work to do.
> >
> > > I've documented my experiences on my blog:
> > >
> > > http://howardlewisship.com/blog/2004/10/upgraded-hivemind-to-forrest-06.html
> >
> > I will check it out soon.
> >
> > > Results are visible online:
> > >
> > > http://jakarta.apache.org/hivemind/
> >
> > Great. I see that the breadcrumb trail has one extra "HiveMind".
> > You probably need to tweak your skinconf.xml to remove that.
> >
> > > There's definately a bug afoot where the system thinks all
> > > "index.html" files are exactly the same, regardless of the folder!
> >
> > Well this works with no problems for other sites,
> > so it must be something peculiar to yours.
> >
> > Looking for the differences between your site.xml
> > and the one for our Forrest site. For each menu
> > that belongs to a "tab", we have a "href" attribute
> > on its top-level element to point to the directory,
> > e.g. on your <hivemind-examples> element.
> >
> > --
> > David Crossley
> >
> >
>
Issues upgrading from 0.5 to 0.6
Posted by Howard Lewis Ship <hl...@gmail.com>.
I'm aware of what I should be doing and much of it used to work in Forrest 0.5.
See the diffs:
http://cvs.apache.org/viewcvs.cgi/jakarta-hivemind/src/documentation/content/xdocs/site.xml?r1=1.26%3Arelease-1-0&tr1=1.28&r2=text&tr2=1.28&diff_format=h
I had to strip out a lot of stuff that makes sense to work around bugs in 0.6.
I'm still finding more problems; for example when trying to build
wholesite.xml, I get:
[java] X [0] wholesite.html
BROKEN: java.lang.RuntimeException:
org.apache.cocoon.ResourceNotFoundException: Resource not found.: o
rg.apache.excalibur.source.SourceNotFoundException:
file:/C:/workspace/jakarta-hivemind/target/forrest-composite/content/xdocs/hivedocs/index.xml
doesn't exist.
Even though my cli.xconf contains:
<exclude pattern="hivedocs/**"/>
<exclude pattern="**/hivedocs/**"/>
<exclude pattern="**/apidocs/**"/>
<exclude pattern="**/clover/**"/>
I also just noticed that top-level, non-menu elements in my site.xml
don't appear. Example:
<reference label="Reference">
<services label="Services" href="services.html"/>
<configurations label="Configurations" href="configurations.html"/>
<hivedoc label="HiveDoc" href="hivedoc.html"/>
<descriptor label="Module Descriptor" href="descriptor.html"/>
<rules label="Contribution Processing Rules" href="rules.html"/>
<dependencies label="Dependencies" href="dependencies.html"/>
</reference>
<changes label="Change Log" href="changes.html"/>
<todo label="TODO" href="todo.html"/>
<mailinglists label="Mailing Lists"
href="http://jakarta.apache.org/site/mail2.html#HiveMind"/>
<downloads href="downloads.html" label="Downloads"/>
<bugs href="http://issues.apache.org/jira/secure/BrowseProject.jspa?id=10500"
label="Bugs"/>
<cvs href="cvs.html" label="CVS Access"/>
<tutorials label="Tutorials and Information">
The "Reference" and "Tutorials and Information" menus appear, but none
of the others do.
On 27 Oct 2004 12:46:05 +1000, David Crossley <cr...@apache.org> wrote:
> Howard Lewis Ship wrote:
> > I eventually did get the HiveMind site building properly, but it took
> > a LOT of effort.
>
> Phew. Very glad to see that you got there, and that
> we could help in some places. Your situation was extra
> difficult due to the integration of Forrest into your
> build system. That should be possible, so we have some
> work to do.
>
> > I've documented my experiences on my blog:
> >
> > http://howardlewisship.com/blog/2004/10/upgraded-hivemind-to-forrest-06.html
>
> I will check it out soon.
>
> > Results are visible online:
> >
> > http://jakarta.apache.org/hivemind/
>
> Great. I see that the breadcrumb trail has one extra "HiveMind".
> You probably need to tweak your skinconf.xml to remove that.
>
> > There's definately a bug afoot where the system thinks all
> > "index.html" files are exactly the same, regardless of the folder!
>
> Well this works with no problems for other sites,
> so it must be something peculiar to yours.
>
> Looking for the differences between your site.xml
> and the one for our Forrest site. For each menu
> that belongs to a "tab", we have a "href" attribute
> on its top-level element to point to the directory,
> e.g. on your <hivemind-examples> element.
>
> --
> David Crossley
>
>
--
Howard M. Lewis Ship
Independent J2EE / Open-Source Java Consultant
Creator, Jakarta Tapestry
Creator, Jakarta HiveMind
http://howardlewisship.com
Re: [RESOLUTION] Upgrade to 0.6: validation issues
Posted by David Crossley <cr...@apache.org>.
Howard Lewis Ship wrote:
> I eventually did get the HiveMind site building properly, but it took
> a LOT of effort.
Phew. Very glad to see that you got there, and that
we could help in some places. Your situation was extra
difficult due to the integration of Forrest into your
build system. That should be possible, so we have some
work to do.
> I've documented my experiences on my blog:
>
> http://howardlewisship.com/blog/2004/10/upgraded-hivemind-to-forrest-06.html
I will check it out soon.
> Results are visible online:
>
> http://jakarta.apache.org/hivemind/
Great. I see that the breadcrumb trail has one extra "HiveMind".
You probably need to tweak your skinconf.xml to remove that.
> There's definately a bug afoot where the system thinks all
> "index.html" files are exactly the same, regardless of the folder!
Well this works with no problems for other sites,
so it must be something peculiar to yours.
Looking for the differences between your site.xml
and the one for our Forrest site. For each menu
that belongs to a "tab", we have a "href" attribute
on its top-level element to point to the directory,
e.g. on your <hivemind-examples> element.
--
David Crossley
[RESOLUTION] Upgrade to 0.6: validation issues
Posted by Howard Lewis Ship <hl...@gmail.com>.
I eventually did get the HiveMind site building properly, but it took
a LOT of effort.
I've documented my experiences on my blog:
http://howardlewisship.com/blog/2004/10/upgraded-hivemind-to-forrest-06.html
Results are visible online:
http://jakarta.apache.org/hivemind/
There's definately a bug afoot where the system thinks all
"index.html" files are exactly the same, regardless of the folder!
On Thu, 21 Oct 2004 09:21:35 -0700, Clay Leeds <cl...@medata.com> wrote:
> On Oct 21, 2004, at 7:23 AM, Howard Lewis Ship wrote:
> > I'm getting closer, but still no dice.
> >
> > The HiveMind site is multiple levels; it has subdirectories for each
> > module.
> >
> > What I'm seeing is that the index.html in the subdirectories ends up
> > with the exact same content (that is, byte-for-byte the same file) as
> > the root index.html. Not only is the content wrong, but the relative
> > URLs are broken (to the skin directory, to pick up images and
> > stylesheets).
> >
> > I actually re-ran the build using Forrest command line:
> >
> > C:\workspace\jakarta-hivemind>forrest
>
> [..]
>
> > X [0] wholesite.html
> > BROKEN: java.lang.RuntimeException:
> > org.apache.cocoon.ResourceNotFoundException: Resource not found.:
> > org.apach
> > e.excalibur.source.SourceNotFoundException:
>
> I would recommend you turn off the 'wholesite.html' until this issue is
> resolved.
>
> > file:/C:/workspace/jakarta-hivemind/target/forrest-composite/content/
> > xdocs/HiveMind-QuickReference.xml
> > doesn't exist.
>
> [..]
>
> > X [0] wholesite.pdf BROKEN:
> > org.apache.fop.apps.FOPException: No flow in page-sequence
>
> and turn off wholesite.pdf too.
>
> [..]
>
> > BUILD FAILED
> > C:\workspace\jakarta-hivemind\ext-package\apache-forrest
> > -0.6\src\core\targets\site.xml:43:
> > Java returned: 1
> >
> > Total time: 1 minute 0 seconds
> >
> > C:\workspace\jakarta-hivemind>
> >
> > I see that the forrest docs split out across multiple folders, so I
> > can't figure out what my be different in my environment.
> >
> > This only affects the index.html in each sub-directory. The other
> > files in each sub-directory come out correctly.
> >
> > Can you think of what might cause a problem like this? It's as if
> > Cocoon was saying "index.html? that looks familiar, I'll just write
> > out the one I just rendered" ... and its ignoring the fact that its a
> > different directory.
>
> This is indeed strange, and I don't know what would cause this. Perhaps
> they all have the same 'id' in site.xml or something silly like that.
>
> Web Maestro Clay
> --
> Clay Leeds - <cl...@medata.com>
> Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
> PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
>
>
--
Howard M. Lewis Ship
Independent J2EE / Open-Source Java Consultant
Creator, Jakarta Tapestry
Creator, Jakarta HiveMind
http://howardlewisship.com
Re: Upgrade to 0.6: validation issues
Posted by Clay Leeds <cl...@medata.com>.
On Oct 21, 2004, at 7:23 AM, Howard Lewis Ship wrote:
> I'm getting closer, but still no dice.
>
> The HiveMind site is multiple levels; it has subdirectories for each
> module.
>
> What I'm seeing is that the index.html in the subdirectories ends up
> with the exact same content (that is, byte-for-byte the same file) as
> the root index.html. Not only is the content wrong, but the relative
> URLs are broken (to the skin directory, to pick up images and
> stylesheets).
>
> I actually re-ran the build using Forrest command line:
>
> C:\workspace\jakarta-hivemind>forrest
[..]
> X [0] wholesite.html
> BROKEN: java.lang.RuntimeException:
> org.apache.cocoon.ResourceNotFoundException: Resource not found.:
> org.apach
> e.excalibur.source.SourceNotFoundException:
I would recommend you turn off the 'wholesite.html' until this issue is
resolved.
> file:/C:/workspace/jakarta-hivemind/target/forrest-composite/content/
> xdocs/HiveMind-QuickReference.xml
> doesn't exist.
[..]
> X [0] wholesite.pdf BROKEN:
> org.apache.fop.apps.FOPException: No flow in page-sequence
and turn off wholesite.pdf too.
[..]
> BUILD FAILED
> C:\workspace\jakarta-hivemind\ext-package\apache-forrest
> -0.6\src\core\targets\site.xml:43:
> Java returned: 1
>
> Total time: 1 minute 0 seconds
>
> C:\workspace\jakarta-hivemind>
>
> I see that the forrest docs split out across multiple folders, so I
> can't figure out what my be different in my environment.
>
> This only affects the index.html in each sub-directory. The other
> files in each sub-directory come out correctly.
>
> Can you think of what might cause a problem like this? It's as if
> Cocoon was saying "index.html? that looks familiar, I'll just write
> out the one I just rendered" ... and its ignoring the fact that its a
> different directory.
This is indeed strange, and I don't know what would cause this. Perhaps
they all have the same 'id' in site.xml or something silly like that.
Web Maestro Clay
--
Clay Leeds - <cl...@medata.com>
Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
Re: Upgrade to 0.6: validation issues
Posted by Howard Lewis Ship <hl...@gmail.com>.
I'm getting closer, but still no dice.
The HiveMind site is multiple levels; it has subdirectories for each module.
What I'm seeing is that the index.html in the subdirectories ends up
with the exact same content (that is, byte-for-byte the same file) as
the root index.html. Not only is the content wrong, but the relative
URLs are broken (to the skin directory, to pick up images and
stylesheets).
I actually re-ran the build using Forrest command line:
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/src/documentation/conf/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 = C:\workspace\jakarta-hivemind/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 22 files to C:\workspace\jakarta-hivemind\target\docs\skin\images
Copying 14 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
^ hivedocs/index.html
^ hivemind/apidocs/index.html
^ hivemind/clover/index.html
^ hivemind-lib/apidocs/index.html
^ hivemind-lib/clover/index.html
^ hivemind-examples/apidocs/index.html
^ hivemind-examples/hivedocs/index.html
^ hivemind-examples/clover/index.html
* [1/63] [63/71] 5.217s 24.1Kb linkmap.html
^ hivemind/apidocs/index.html
^ hivemind/clover/index.html
^ hivedocs/config/hivemind.ServiceModels.html
^
hivemind/apidocs/org/apache/hivemind/internal/ServiceModelFactory.html
* [2/63] [1/32] 1.082s 7.6Kb hivemind/ServiceModels.html
^ hivedocs/index.html
* [3/62] [0/35] 0.651s 7.9Kb cvs.html
^ hivedocs/index.html
* [4/66] [5/46] 1.752s 27.0Kb changes.html
^ hivedocs/index.html
^
hivemind/apidocs/org/apache/hivemind/test/HiveMindTestCase.html
* [6/64] [0/37] 0.791s 11.2Kb dependencies.html
^ hivemind-lib/apidocs/index.html
^ hivemind-lib/clover/index.html
^ hivedocs/module/hivemind.lib.html
* [7/63] [0/28] 0.54s 6.0Kb hivemind-lib/index.html
* [8/62] [0/0] 0.681s 2.0Kb changes.rss
^ hivemind-lib/apidocs/index.html
^ hivemind-lib/clover/index.html
^
hivedocs/service/hivemind.lib.RemoteExceptionCoordinator.html
^
hivemind/apidocs/org/apache/hivemind/lib/RemoteExceptionCoordinator.html
^
hivemind/apidocs/org/apache/hivemind/lib/RemoteExceptionListener.html
* [9/61] [0/29] 0.852s 6.8Kb
hivemind-lib/RemoteExceptionCoordinator.html
^ hivedocs/index.html
^
hivemind/apidocs/org/apache/hivemind/impl/SystemPropertiesSymbolSource.html
^
hivemind/apidocs/org/apache/hivemind/Element.html
* [10/60] [0/52] 0.871s 23.2Kb configurations.html
^ hivedocs/index.html
^
hivemind/apidocs/org/apache/hivemind/impl/RegistryBuilder.html
^
hivemind/apidocs/org/apache/hivemind/Registry.html
* [11/59] [0/41] 0.771s 11.4Kb multithreading.html
* [13/57] [0/0] 1.152s 24.5Kb hivemind-lib/
^ hivedocs/index.html
* [14/56] [0/35] 0.521s 8.1Kb todo.html
^ hivedocs/index.html
* [16/54] [0/41] 0.51s 9.3Kb hivedoc.html
X [0] wholesite.html
BROKEN: java.lang.RuntimeException:
org.apache.cocoon.ResourceNotFoundException: Resource not found.:
org.apach
e.excalibur.source.SourceNotFoundException:
file:/C:/workspace/jakarta-hivemind/target/forrest-composite/content/xdocs/HiveMind-QuickReference.xml
doesn't exist.
^ hivemind-lib/apidocs/index.html
^ hivemind-lib/clover/index.html
^
hivedocs/service/hivemind.lib.ServicePropertyFactory.html
* [19/51] [0/28] 0.6s 7.3Kb hivemind-lib/ServicePropertyFactory.html
* [21/49] [0/0] 1.673s 348b skin/images/rc-b-l-15-1body-2menu-3menu.png
^ hivedocs/index.html
* [22/48] [0/35] 0.771s 19.8Kb license-report.html
^ hivedocs/index.html
* [25/45] [0/35] 0.441s 8.9Kb downloads.html
^ hivedocs/index.html
^
hivemind/apidocs/org/apache/hivemind/schema/Rule.html
^
hivemind/apidocs/org/apache/hivemind/schema/Rule.html
^
hivemind/apidocs/org/apache/hivemind/schema/Translator.html
^
hivemind-lib/apidocs/org/apache/hivemind/lib/BeanFactory.html
^
hivemind/apidocs/org/apache/hivemind/Resource.html
^
hivemind/apidocs/org/apache/hivemind/schema/rules/SmartTranslator.html
* [26/44] [0/54] 1.272s 31.7Kb rules.html
^ hivemind/apidocs/index.html
^ hivemind/clover/index.html
^
hivedocs/config/hivemind.FactoryDefaults.html
* [27/43] [0/31] 0.881s 7.1Kb hivemind/FactoryDefaults.html
^ hivemind-examples/apidocs/index.html
^ hivemind-examples/hivedocs/index.html
^ hivemind-examples/clover/index.html
^
hivemind/apidocs/org/apache/hivemind/ServiceInterceptorFactory.html
^
hivemind/apidocs/org/apache/hivemind/InterceptorStack.html
^
hivemind/apidocs/org/apache/hivemind/Module.html
* [28/42] [0/28] 0.751s 20.7Kb hivemind-examples/logging.html
^ hivemind-lib/apidocs/index.html
^ hivemind-lib/clover/index.html
^
hivedocs/service/hivemind.lib.PipelineFactory.html
* [29/42] [1/30] 0.931s 11.5Kb hivemind-lib/PipelineFactory.html
^ hivedocs/index.html
^
hivemind/apidocs/org/apache/hivemind/impl/RegistryBuilder.html
^
hivemind/apidocs/org/apache/hivemind/Registry.html
* [31/41] [1/39] 0.631s 20.6Kb bootstrap.html
^ hivemind/apidocs/index.html
^ hivemind/clover/index.html
^
hivedocs/service/hivemind.BuilderFactory.html
^
hivemind/apidocs/org/apache/hivemind/ClassResolver.html
^
hivemind/apidocs/org/apache/hivemind/ErrorHandler.html
^
hivemind/apidocs/org/apache/hivemind/Messages.html
^
hivemind/apidocs/org/apache/hivemind/Resource.html
* [32/40] [0/35] 0.841s 27.1Kb hivemind/BuilderFactory.html
^ hivemind-lib/apidocs/index.html
^ hivemind-lib/clover/index.html
^
hivedocs/service/hivemind.lib.NameLookup.html
* [33/39] [0/27] 0.892s 6.7Kb hivemind-lib/NameLookup.html
^ hivemind/apidocs/index.html
^ hivemind/clover/index.html
^
hivemind/apidocs/org/apache/hivemindant/ManifestClassPath.html
* [34/38] [0/31] 0.53s 9.8Kb hivemind/ant/ManifestClassPath.html
^ hivemind/apidocs/index.html
^ hivemind/clover/index.html
^ hivedocs/config/hivemind.SymbolSources.html
^
hivemind/apidocs/org/apache/hivemind/SymbolSource.html
* [36/36] [0/32] 0.471s 7.8Kb hivemind/SymbolSources.html
X [0] wholesite.pdf BROKEN:
org.apache.fop.apps.FOPException: No flow in page-sequence
^ hivemind-lib/apidocs/index.html
^ hivemind-lib/clover/index.html
^
hivedocs/service/hivemind.lib.BeanFactoryBuilder.html
^
hivemind-lib/apidocs/org/apache/hivemind/lib/BeanFactory.html
* [39/33] [0/28] 0.491s 9.1Kb hivemind-lib/BeanFactoryBuilder.html
^ hivedocs/index.html
* [40/32] [0/38] 0.611s 15.3Kb override.html
^ hivemind/apidocs/index.html
^ hivemind/clover/index.html
^
hivemind/apidocs/org/apache/hivemind/ant/ConstructRegistry.html
* [41/31] [0/31] 0.52s 9.3Kb hivemind/ant/ConstructRegistry.html
^ hivemind-examples/apidocs/index.html
^ hivemind-examples/hivedocs/index.html
^ hivemind-examples/clover/index.html
* [42/30] [0/22] 0.751s 7.3Kb hivemind-examples/index.html
^ hivemind/apidocs/index.html
^ hivemind/clover/index.html
^
hivedocs/service/hivemind.ThreadLocalStorage.html
^
hivemind/apidocs/org/apache/hivemind/service/ThreadLocalStorage.html
* [43/29] [0/32] 0.481s 7.2Kb hivemind/ThreadLocalStorage.html
^ hivemind/apidocs/index.html
^ hivemind/clover/index.html
^ hivedocs/config/hivemind.Translators.html
^
hivemind/apidocs/org/apache/hivemind/schema/Translator.html
* [44/28] [0/32] 0.481s 7.5Kb hivemind/Translators.html
^ hivemind-lib/apidocs/index.html
^ hivemind-lib/clover/index.html
^
hivedocs/service/hivemind.lib.EJBProxyFactory.html
^
hivemind/apidocs/org/apache/hivemind/lib/NameLookup.html
* [45/27] [0/28] 0.871s 7.3Kb hivemind-lib/EJBProxyFactory.html
^ hivedocs/index.html
^
hivemind/apidocs/org/apache/hivemind/Messages.html
^
hivemind/apidocs/org/apache/hivemind/Registry.html
^
hivemind/apidocs/org/apache/hivemind/impl/RegistryBuilder.html
* [46/26] [0/41] 0.461s 10.5Kb localization.html
^ hivemind-lib/apidocs/index.html
^ hivemind-lib/clover/index.html
^
hivedocs/service/hivemind.lib.DefaultImplementationBuilder.html
^
hivemind-lib/apidocs/org/apache/hivemind/lib/DefaultImplementationBuilder.html
* [47/25] [0/28] 0.46s 6.5Kb
hivemind-lib/DefaultImplementationBuilder.html
^ hivemind/apidocs/index.html
^ hivemind/clover/index.html
^
hivedocs/config/hivemind.ObjectProviders.html
^
hivemind-lib/apidocs/org/apache/hivemind/lib/BeanFactory.html
* [48/24] [0/32] 0.591s 10.0Kb hivemind/ObjectProviders.html
^ hivedocs/index.html
* [50/22] [0/36] 0.551s 11.8Kb ioc.html
^ hivemind/apidocs/index.html
^ hivemind/clover/index.html
^
hivedocs/service/hivemind.LoggingInterceptor.html
^
hivemind/apidocs/org/apache/hivemind/methodmatch/MethodMatcher.html
* [51/21] [0/32] 0.47s 8.2Kb hivemind/LoggingInterceptor.html
^ hivedocs/index.html
* [52/21] [1/39] 0.481s 24.5Kb index.html
^ hivedocs/index.html
^
hivemind/apidocs/org/apache/hivemind/servlet/HiveMindFilter.html
^
hivemind/apidocs/org/apache/hivemind/Registry.html
* [54/19] [0/37] 0.461s 9.6Kb filter.html
^ hivemind-examples/apidocs/index.html
^ hivemind-examples/hivedocs/index.html
^ hivemind-examples/clover/index.html
^
hivemind-examples/hivedocs/schema/panorama.startup.Tasks.html
^
hivemind-examples/clover/com/panorama/startup/impl/pkg-summary.html
* [55/18] [0/25] 1.001s 27.9Kb hivemind-examples/panorama.html
^ hivedocs/index.html
^
hivemind/apidocs/org/apache/hivemind/ServiceImplementationFactory.html
^
hivemind/apidocs/org/apache/hivemind/ServiceInterceptorFactory.html
^ hivedocs/module/hivemind.html
^
hivemind/apidocs/org/apache/hivemind/Discardable.html
^
hivemind/apidocs/org/apache/hivemind/events/RegistryShutdownListener.html
^
hivemind/apidocs/org/apache/hivemind/PoolManageable.html
^
hivemind/apidocs/org/apache/hivemind/Registry.html
* [56/18] [1/59] 0.801s 33.4Kb services.html
* [57/17] [0/0] 0.391s 24.5Kb hivemind-examples/
^ hivemind-lib/apidocs/index.html
^ hivemind-lib/clover/index.html
^
hivedocs/service/hivemind.lib.SpringLookupFactory.html
^
hivedocs/service/hivemind.lib.DefaultSpringBeanFactoryHolder.html
^
hivemind-lib/apidocs/org/apache/hivemind/lib/SpringBeanFactoryHolder.html
^
hivemind-lib/apidocs/org/apache/hivemind/lib/SpringBeanFactorySource.html
* [58/16] [0/30] 0.871s 7.6Kb hivemind-lib/SpringLookupFactory.html
^ hivemind-lib/apidocs/index.html
^ hivemind-lib/clover/index.html
^
hivedocs/service/hivemind.lib.PlaceholderFactory.html
* [59/15] [0/27] 0.571s 6.4Kb hivemind-lib/PlaceholderFactory.html
^ hivemind/apidocs/index.html
^ hivemind/clover/index.html
^ hivedocs/module/hivemind.html
* [60/14] [0/32] 0.491s 6.6Kb hivemind/index.html
^ hivemind/apidocs/index.html
^ hivemind/clover/index.html
^
hivedocs/config/hivemind.ApplicationDefaults.html
* [61/13] [0/31] 0.61s 7.1Kb hivemind/ApplicationDefaults.html
* [63/11] [0/0] 0.56s 2.6Kb skin/basic.css
* [64/10] [0/0] 0.441s 24.5Kb hivemind/
* [67/7] [0/0] 0.391s 24.5Kb
* [68/18] [12/12] 0.37s 11.9Kb skin/screen.css
* [69/17] [0/0] 0.07s 215b
skin/images/rc-t-r-5-1header-2searchbox-3searchbox.png
* [70/16] [0/0] 0.09s 215b
skin/images/rc-t-r-5-1header-2tab-unselected-3tab-unselected.png
* [71/15] [0/0] 0.09s 214b
skin/images/rc-t-r-5-1header-2tab-selected-3tab-selected.png
* [73/13] [0/0] 0.11s 207b
skin/images/rc-t-l-5-1header-2searchbox-3searchbox.png
* [74/12] [0/0] 0.08s 207b
skin/images/rc-t-l-5-1header-2tab-unselected-3tab-unselected.png
* [76/10] [0/0] 0.08s 319b skin/images/rc-b-r-15-1body-2menu-3menu.png
* [77/9] [0/0] 0.08s 201b
skin/images/rc-b-r-5-1header-2tab-selected-3tab-selected.png
* [78/8] [0/0] 0.07s 207b
skin/images/rc-t-l-5-1header-2tab-selected-3tab-selected.png
* [79/7] [0/0] 0.08s 390b skin/images/rc-t-r-15-1body-2menu-3menu.png
^ hivemind/apidocs/index.html
^ hivemind/clover/index.html
^ hivedocs/config/hivemind.EagerLoad.html
* [80/6] [0/31] 0.471s 7.5Kb hivemind/EagerLoad.html
* [81/5] [0/0] 0.07s 1.1Kb skin/print.css
^ hivemind-examples/apidocs/index.html
^ hivemind-examples/hivedocs/index.html
^ hivemind-examples/clover/index.html
* [82/4] [0/25] 0.881s 11.6Kb hivemind-examples/calc.html
* [83/3] [0/0] 0.11s 3.9Kb skin/profile.css
^ hivedocs/index.html
^
hivemind/apidocs/org/apache/hivemind/Registry.html
^
hivemind/apidocs/org/apache/hivemind/Element.html
^
hivemind/apidocs/org/apache/hivemind/ServiceInterceptorFactory.html
^
hivemind/apidocs/org/apache/hivemind/ServiceImplementationFactory.html
* [85/1] [0/91] 1.091s 40.0Kb descriptor.html
^ hivemind/apidocs/index.html
^ hivemind/clover/index.html
^
hivemind/apidocs/org/apache/hivemind/events/RegistryShutdownListener.html
* [86/0] [0/31] 0.561s 7.0Kb hivemind/ShutdownCoordinator.html
Total time: 0 minutes 53 seconds, Site size: 763,285 Site pages: 66
BUILD FAILED
C:\workspace\jakarta-hivemind\ext-package\apache-forrest-0.6\src\core\targets\site.xml:43:
Java returned: 1
Total time: 1 minute 0 seconds
C:\workspace\jakarta-hivemind>
I see that the forrest docs split out across multiple folders, so I
can't figure out what my be different in my environment.
This only affects the index.html in each sub-directory. The other
files in each sub-directory come out correctly.
Can you think of what might cause a problem like this? It's as if
Cocoon was saying "index.html? that looks familiar, I'll just write
out the one I just rendered" ... and its ignoring the fact that its a
different directory.
On Thu, 21 Oct 2004 16:04:00 +0200, Nicola Ken Barozzi
<ni...@apache.org> wrote:
> Howard Lewis Ship wrote:
> > Sometimes the process of complaining (sorry, folks) leads you to the result.
> >
> > Had to set project.configfile in my forrest.properties to point at my
> > updated version.
>
> Does this mean that now it works? :-)
>
> BTW, consider switching to the new pelt skin. The Hivemind site is
> exactly a type of site (large navigation) that should benefit from the
> smaller font sizes.
>
> --
>
>
> Nicola Ken Barozzi nicolaken@apache.org
> - verba volant, scripta manent -
> (discussions get forgotten, just code remains)
> ---------------------------------------------------------------------
>
>
--
Howard M. Lewis Ship
Independent J2EE / Open-Source Java Consultant
Creator, Jakarta Tapestry
Creator, Jakarta HiveMind
http://howardlewisship.com
Re: Upgrade to 0.6: validation issues
Posted by Nicola Ken Barozzi <ni...@apache.org>.
Howard Lewis Ship wrote:
> Sometimes the process of complaining (sorry, folks) leads you to the result.
>
> Had to set project.configfile in my forrest.properties to point at my
> updated version.
Does this mean that now it works? :-)
BTW, consider switching to the new pelt skin. The Hivemind site is
exactly a type of site (large navigation) that should benefit from the
smaller font sizes.
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
Re: Upgrade to 0.6: validation issues
Posted by Howard Lewis Ship <hl...@gmail.com>.
Sometimes the process of complaining (sorry, folks) leads you to the result.
Had to set project.configfile in my forrest.properties to point at my
updated version.
On Wed, 20 Oct 2004 21:11:39 -0400, Howard Lewis Ship <hl...@gmail.com> wrote:
> Getting closer; has anything change in conf/cli.xconf?
>
> I'm getting errors like:
>
> [java] X [0]
> hivedocs/service/hivemind.lib.DefaultImplementationBuilder.html
> BROKEN: C:
> mposite\content\xdocs\hivedocs\service\hivemind.lib.DefaultImplementationBuilder.xml
> (The system cannot find the path specified)
>
> Even though my conf/xli.xconf contains:
>
> <exclude pattern="hivedocs/**"/>
> <exclude pattern="**/hivedocs/**"/>
> <exclude pattern="**/apidocs/**"/>
> <exclude pattern="**/clover/**"/>
>
>
>
>
> On Wed, 20 Oct 2004 17:40:22 -0400, Howard Lewis Ship <hl...@gmail.com> wrote:
> > Sounds fine; what I do is assemple xdoc and other content files from
> > my top-level project and my 2nd level modules into a single directory,
> > the "forrest-composite". I then execute forrest against that to
> > generate my final output.
> >
> > What I've found from further experimentation is that my Forrest 0.5
> > skinconf.xml and cli.xconf caused problems; I've deleted them and need
> > to recreate some of their information (such as, paths not to pursue).
> >
> >
> >
> >
> > On Wed, 20 Oct 2004 14:01:10 +0200, Nicola Ken Barozzi
> > <ni...@apache.org> wrote:
> > > Howard Lewis Ship wrote:
> > > ...
> > > > I kind of object to "bad" being equated with "non-standard". Forrest
> > > > is the non-standard here, since it's a very common practice to put all
> > > > derived/compiled/generated files somewhere under target (which
> > > > simplifies any implementation of a clean target).
> > >
> > > Everyone has his idea of what a standard is :-)
> > >
> > > Our latest months have been devoted to making it possible for Forrest
> > > not to copy anything to be able to build, and that is where our
> > > "standard" idea comes from ATM, although we are well aware of what other
> > > projects are used to do.
> > >
> > > ATM the integration of other pregenerated docs in the Forrest docs is
> > > suboptimal to say the least: it's necessary to reassemble the Forrest
> > > docs along with pregenerated ones in a single directory (as you say
> > > under /target, I was used to /build).
> > >
> > > With the next release we intend to insert a 'locationmap', with which
> > > one can mount other paths. This means that you could keep your source
> > > files in src, and simply point Forrest to look for other build-generated
> > > files under /target or wherever.
> > >
> > > Would this approach suit your needs better?
> > >
> > > --
> > > Nicola Ken Barozzi nicolaken@apache.org
> > > - verba volant, scripta manent -
> > > (discussions get forgotten, just code remains)
> > > ---------------------------------------------------------------------
> > >
> > >
> >
> > --
> > Howard M. Lewis Ship
> > Independent J2EE / Open-Source Java Consultant
> > Creator, Jakarta Tapestry
> > Creator, Jakarta HiveMind
> > http://howardlewisship.com
> >
>
> --
> Howard M. Lewis Ship
> Independent J2EE / Open-Source Java Consultant
> Creator, Jakarta Tapestry
> Creator, Jakarta HiveMind
> http://howardlewisship.com
>
--
Howard M. Lewis Ship
Independent J2EE / Open-Source Java Consultant
Creator, Jakarta Tapestry
Creator, Jakarta HiveMind
http://howardlewisship.com
using a project cli.xconf (Was: Upgrade to 0.6: validation issues)
Posted by David Crossley <cr...@apache.org>.
(Bringing over from user list.)
In the advice below, i had to specify:
project.configfile=${project.home}/src/documentation/conf/cli.xconf
I expected to be able to specify:
project.configfile=${project.conf-dir}/cli.xconf
(and of course expose those properties project.content-dir
and project.conf-dir).
However that causes issues so i use the long form.
------
ERROR:
/asf/apache-forrest-0.6/src/core/context/src/documentation/conf/cli.xconf (No such file or directory)
------
In other words it is trying beneath $FORREST_HOME
rather that in my project space. Why?
--David
David Crossley wrote:
> Howard Lewis Ship wrote:
> > Getting closer; has anything change in conf/cli.xconf?
>
> When the project uses one, it needs to add an entry to
> forrest.properties file.
> project.configfile=${project.home}/src/documentation/conf/cli.xconf
>
> I imagine that this change is a result from the new "copyless"
> behaviour. We now need to explicitly declare these over-riding
> configuration files.
>
> --David
Re: Upgrade to 0.6: validation issues
Posted by David Crossley <cr...@apache.org>.
Howard Lewis Ship wrote:
> Getting closer; has anything change in conf/cli.xconf?
When the project uses one, it needs to add an entry to
forrest.properties file.
project.configfile=${project.home}/src/documentation/conf/cli.xconf
I imagine that this change is a result from the new "copyless"
behaviour. We now need to explicitly declare these over-riding
configuration files.
--David
> I'm getting errors like:
>
> [java] X [0]
> hivedocs/service/hivemind.lib.DefaultImplementationBuilder.html
> BROKEN: C:
> mposite\content\xdocs\hivedocs\service\hivemind.lib.DefaultImplementationBuilder.xml
> (The system cannot find the path specified)
>
> Even though my conf/xli.xconf contains:
>
> <exclude pattern="hivedocs/**"/>
> <exclude pattern="**/hivedocs/**"/>
> <exclude pattern="**/apidocs/**"/>
> <exclude pattern="**/clover/**"/>
>
> Howard Lewis Ship wrote:
> > Sounds fine; what I do is assemple xdoc and other content files from
> > my top-level project and my 2nd level modules into a single directory,
> > the "forrest-composite". I then execute forrest against that to
> > generate my final output.
> >
> > What I've found from further experimentation is that my Forrest 0.5
> > skinconf.xml and cli.xconf caused problems; I've deleted them and need
> > to recreate some of their information (such as, paths not to pursue).
Re: Upgrade to 0.6: validation issues
Posted by Howard Lewis Ship <hl...@gmail.com>.
Getting closer; has anything change in conf/cli.xconf?
I'm getting errors like:
[java] X [0]
hivedocs/service/hivemind.lib.DefaultImplementationBuilder.html
BROKEN: C:
mposite\content\xdocs\hivedocs\service\hivemind.lib.DefaultImplementationBuilder.xml
(The system cannot find the path specified)
Even though my conf/xli.xconf contains:
<exclude pattern="hivedocs/**"/>
<exclude pattern="**/hivedocs/**"/>
<exclude pattern="**/apidocs/**"/>
<exclude pattern="**/clover/**"/>
On Wed, 20 Oct 2004 17:40:22 -0400, Howard Lewis Ship <hl...@gmail.com> wrote:
> Sounds fine; what I do is assemple xdoc and other content files from
> my top-level project and my 2nd level modules into a single directory,
> the "forrest-composite". I then execute forrest against that to
> generate my final output.
>
> What I've found from further experimentation is that my Forrest 0.5
> skinconf.xml and cli.xconf caused problems; I've deleted them and need
> to recreate some of their information (such as, paths not to pursue).
>
>
>
>
> On Wed, 20 Oct 2004 14:01:10 +0200, Nicola Ken Barozzi
> <ni...@apache.org> wrote:
> > Howard Lewis Ship wrote:
> > ...
> > > I kind of object to "bad" being equated with "non-standard". Forrest
> > > is the non-standard here, since it's a very common practice to put all
> > > derived/compiled/generated files somewhere under target (which
> > > simplifies any implementation of a clean target).
> >
> > Everyone has his idea of what a standard is :-)
> >
> > Our latest months have been devoted to making it possible for Forrest
> > not to copy anything to be able to build, and that is where our
> > "standard" idea comes from ATM, although we are well aware of what other
> > projects are used to do.
> >
> > ATM the integration of other pregenerated docs in the Forrest docs is
> > suboptimal to say the least: it's necessary to reassemble the Forrest
> > docs along with pregenerated ones in a single directory (as you say
> > under /target, I was used to /build).
> >
> > With the next release we intend to insert a 'locationmap', with which
> > one can mount other paths. This means that you could keep your source
> > files in src, and simply point Forrest to look for other build-generated
> > files under /target or wherever.
> >
> > Would this approach suit your needs better?
> >
> > --
> > Nicola Ken Barozzi nicolaken@apache.org
> > - verba volant, scripta manent -
> > (discussions get forgotten, just code remains)
> > ---------------------------------------------------------------------
> >
> >
>
> --
> Howard M. Lewis Ship
> Independent J2EE / Open-Source Java Consultant
> Creator, Jakarta Tapestry
> Creator, Jakarta HiveMind
> http://howardlewisship.com
>
--
Howard M. Lewis Ship
Independent J2EE / Open-Source Java Consultant
Creator, Jakarta Tapestry
Creator, Jakarta HiveMind
http://howardlewisship.com
Re: Upgrade to 0.6: validation issues
Posted by David Crossley <cr...@apache.org>.
Howard Lewis Ship wrote:
> Sounds fine; what I do is assemple xdoc and other content files from
> my top-level project and my 2nd level modules into a single directory,
> the "forrest-composite". I then execute forrest against that to
> generate my final output.
>
> What I've found from further experimentation is that my Forrest 0.5
> skinconf.xml and cli.xconf caused problems; I've deleted them and need
> to recreate some of their information (such as, paths not to pursue).
Regarding the skinconf.xml
The "upgrading doc" does advise that you need to upgrade
your skinconf.xml file:
http://forrest.apache.org/docs/upgrading_06.html#sync
--
David Crossley
Re: Upgrade to 0.6: validation issues
Posted by Howard Lewis Ship <hl...@gmail.com>.
Sounds fine; what I do is assemple xdoc and other content files from
my top-level project and my 2nd level modules into a single directory,
the "forrest-composite". I then execute forrest against that to
generate my final output.
What I've found from further experimentation is that my Forrest 0.5
skinconf.xml and cli.xconf caused problems; I've deleted them and need
to recreate some of their information (such as, paths not to pursue).
On Wed, 20 Oct 2004 14:01:10 +0200, Nicola Ken Barozzi
<ni...@apache.org> wrote:
> Howard Lewis Ship wrote:
> ...
> > I kind of object to "bad" being equated with "non-standard". Forrest
> > is the non-standard here, since it's a very common practice to put all
> > derived/compiled/generated files somewhere under target (which
> > simplifies any implementation of a clean target).
>
> Everyone has his idea of what a standard is :-)
>
> Our latest months have been devoted to making it possible for Forrest
> not to copy anything to be able to build, and that is where our
> "standard" idea comes from ATM, although we are well aware of what other
> projects are used to do.
>
> ATM the integration of other pregenerated docs in the Forrest docs is
> suboptimal to say the least: it's necessary to reassemble the Forrest
> docs along with pregenerated ones in a single directory (as you say
> under /target, I was used to /build).
>
> With the next release we intend to insert a 'locationmap', with which
> one can mount other paths. This means that you could keep your source
> files in src, and simply point Forrest to look for other build-generated
> files under /target or wherever.
>
> Would this approach suit your needs better?
>
> --
> Nicola Ken Barozzi nicolaken@apache.org
> - verba volant, scripta manent -
> (discussions get forgotten, just code remains)
> ---------------------------------------------------------------------
>
>
--
Howard M. Lewis Ship
Independent J2EE / Open-Source Java Consultant
Creator, Jakarta Tapestry
Creator, Jakarta HiveMind
http://howardlewisship.com
Re: Upgrade to 0.6: validation issues
Posted by Nicola Ken Barozzi <ni...@apache.org>.
Howard Lewis Ship wrote:
...
> I kind of object to "bad" being equated with "non-standard". Forrest
> is the non-standard here, since it's a very common practice to put all
> derived/compiled/generated files somewhere under target (which
> simplifies any implementation of a clean target).
Everyone has his idea of what a standard is :-)
Our latest months have been devoted to making it possible for Forrest
not to copy anything to be able to build, and that is where our
"standard" idea comes from ATM, although we are well aware of what other
projects are used to do.
ATM the integration of other pregenerated docs in the Forrest docs is
suboptimal to say the least: it's necessary to reassemble the Forrest
docs along with pregenerated ones in a single directory (as you say
under /target, I was used to /build).
With the next release we intend to insert a 'locationmap', with which
one can mount other paths. This means that you could keep your source
files in src, and simply point Forrest to look for other build-generated
files under /target or wherever.
Would this approach suit your needs better?
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
Re: Upgrade to 0.6: validation issues
Posted by Howard Lewis Ship <hl...@gmail.com>.
I kind of object to "bad" being equated with "non-standard". Forrest
is the non-standard here, since it's a very common practice to put all
derived/compiled/generated files somewhere under target (which
simplifies any implementation of a clean target).
My forrest.properties:
project.name=HiveMind
project.build-dir=${project.home}/target/forrest
project.site-dir=${project.home}/target/docs
project.temp-dir=target/forrest
project.content-dir=target/forrest-composite
forrest.echo=on
project.debuglevel=DEBUG
project.bugtracking-url=http://nagoya.apache.org/jira/browse/
Thanks for pointing me towards this; I just changed
project.temp-dir=${project.home}/target/forrest
And I'm much closer to it working now (though I had to use my earlier
approach ... re-running Forrest's Ant using <java> task).
On 20 Oct 2004 11:31:21 +1000, David Crossley <cr...@apache.org> wrote:
> Howard Lewis Ship wrote:
> > No. I cannot. The structure is very important to the build files,
> > which automatically download forrest. If forrest has a problem with
> > this, then it is broken.
>
> Oh, that certainly makes things complicated. At least
> we might have found your issue.
>
> I suppose that you have needed to change many settings
> in forrest.properties to get that layout to work.
> Please double-check that that file still correlates
> with a fresh forrest.properties obtained from doing
> a 'forrest seed' in some other new directory workspace
> (or just compare with
> apache-forrest-0.6/src/core/fresh-site/forrest.properties).
>
> I see from your "echo-settings" list that the "project.temp-dir"
> has a bad setting. Normally it would be at ${project.home}/build/tmp/
>
> Try adding a specific entry to forrest.properties
> project.temp-dir=/some/hard-coded/pathname/foo
> or somewhere underneath your project, e.g.
> project.temp-dir=${project.home}/foo
>
> --
> David Crossley
>
>
--
Howard M. Lewis Ship
Independent J2EE / Open-Source Java Consultant
Creator, Jakarta Tapestry
Creator, Jakarta HiveMind
http://howardlewisship.com
Re: Upgrade to 0.6: validation issues
Posted by David Crossley <cr...@apache.org>.
Howard Lewis Ship wrote:
> No. I cannot. The structure is very important to the build files,
> which automatically download forrest. If forrest has a problem with
> this, then it is broken.
Oh, that certainly makes things complicated. At least
we might have found your issue.
I suppose that you have needed to change many settings
in forrest.properties to get that layout to work.
Please double-check that that file still correlates
with a fresh forrest.properties obtained from doing
a 'forrest seed' in some other new directory workspace
(or just compare with
apache-forrest-0.6/src/core/fresh-site/forrest.properties).
I see from your "echo-settings" list that the "project.temp-dir"
has a bad setting. Normally it would be at ${project.home}/build/tmp/
Try adding a specific entry to forrest.properties
project.temp-dir=/some/hard-coded/pathname/foo
or somewhere underneath your project, e.g.
project.temp-dir=${project.home}/foo
--
David Crossley
Re: Upgrade to 0.6: validation issues
Posted by Howard Lewis Ship <hl...@gmail.com>.
No. I cannot. The structure is very important to the build files,
which automatically download forrest. If forrest has a problem with
this, then it is broken.
Again, everything worked like a charm in Forrest 0.5 ... I just want
it to work in 0.6.
On 20 Oct 2004 09:08:28 +1000, David Crossley <cr...@apache.org> wrote:
> Howard Lewis Ship wrote:
> > Nope; even the forrest.bat tool isn't working:
>
> I see some strange paths in the output below.
> It seems that you have Forrest installed in a directory
> underneath your project workspace. This seems to cause
> confusion. Try installing Forrest at
> C:\workspace\apache-forrest-0.6\
> and your project home at
> C:\workspace\jakarta-hivemind\
>
> --David
>
>
>
> > 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 <da...@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
Re: Upgrade to 0.6: validation issues
Posted by David Crossley <cr...@apache.org>.
Howard Lewis Ship wrote:
> Nope; even the forrest.bat tool isn't working:
I see some strange paths in the output below.
It seems that you have Forrest installed in a directory
underneath your project workspace. This seems to cause
confusion. Try installing Forrest at
C:\workspace\apache-forrest-0.6\
and your project home at
C:\workspace\jakarta-hivemind\
--David
> 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 <da...@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
> >
> >
> >
>
Re: Upgrade to 0.6: validation issues
Posted by Howard Lewis Ship <hl...@gmail.com>.
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 <da...@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
Re: Upgrade to 0.6: validation issues
Posted by Dave Brondsema <da...@brondsema.net>.
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
Re: Upgrade to 0.6: validation issues
Posted by Howard Lewis Ship <hl...@gmail.com>.
I tried the antproxy approach first, but the validation didn't work.
I'll revert back to that version and copy the output:
<property name="forrest-package-dir"
value="${external.package.dir}/apache-forrest-0.6"/>
<property name="forrest.home" location="${forrest-package-dir}/src/core"/>
<import file="${forrest.home}/forrest.build.xml"/>
<target name="run-forrest" description="Runs Forrest to generate
final site documentation.">
<announce message="Invoking Forrest ..."/>
<antcall target="site.site"/>
</target>
bash-2.05b$ ant -p
Buildfile: build.xml
Main targets:
available-skins What skins are available?
clean Deletes all derived files in the
project and in each module.
clean-code Deletes compiled code in each module.
clean-ext-packages Delete all downloaded external packages.
dist Build a distribution.
dist-build Constructs final distribution files.
fast-site Generate site documentation from
XDocs only, omitting reports.
forrest.clean * Clean all directories and files
generated during the build
forrestdoc.marshall-documentation Copy static content into the
forrest composite, and generate dynamic reports.
forrestdoc.run-reports Overridden in project or module to
run dynamic reports.
hivebuild.clean Deletes all derived files.
install Reinvokes install in each module.
install-dist Install current distributions.
install-docs Copies the documentation to a
directory and unpacks it remotely.
install-maven Install JARs into Maven
distribution library.
install-skin Install the needed skin from the
remote repository
marshall-documentation Marshall documentation in the
project and in each module.
package-skin Make a package of an existing skin
run * Run Jetty (instant live webapp)
run-forrest Runs Forrest to generate final
site documentation.
run_custom_jetty Run Jetty with configuration file
found in the project
run_default_jetty Run Jetty with configuration file
found in Forrest
seed * Seeds a directory with a
template project doc structure
site Build site documentation using Forrest.
site.site * Generates a static HTML website
for this project
validate Validate all: xdocs, skins, sitemap, etc
validate-sitemap Validate the project sitemaps
validate-skinchoice Validate skin choice
validate-skinconf Validate skinconf
validate-skins Validate skins
validate-stylesheets Validate XSL files
validate-xdocs Validate the project xdocs
war * Generates a dynamic
servlet-based website (a packaged .war file)
webapp Generates a dynamic servlet-based
website (an unpackaged webapp).
webapp-local Generates a dynamic servlet-based
website (an unpackaged webapp). Note this webapp is suitable for
local execution only, use the 'war' or
'webapp' target if you wish to deploy remotely.
Default target: install
Takes many minutes to run, because it isn't using local entity catalogs:
bash-2.05b$ ant fast-site
Buildfile: build.xml
copy-documentation-to-composite:
fast-site:
copy-documentation-to-composite:
copy-documentation-to-composite:
copy-documentation-to-composite:
run-forrest:
[echo]
[echo]
[echo] *** Invoking Forrest ...
[echo]
init-props:
[echo] Loading project specific properties from
C:\workspace\jakarta-hivemind\forrest.properties
[echo] Loading user specific properties from C:\Documents and
Settings\Howard\forrest.properties
[echo] Loading default properties from
C:\workspace\jakarta-hivemind\ext-package\apache-forrest-0.6\src\core\context\default-forrest.properties
echo-settings:
[echo] ------------------------------------------------
[echo] | Forrest template run.
[echo] | Running from ${forrest.home} =
C:\workspace\jakarta-hivemind\ext-package\apache-forrest-0.6\src\core
[echo] | Working on ${project.home} = C:\workspace\jakarta-hivemind
[echo] ------------------------------------------------
[echo] | //where to put the result
[echo] | project.site-dir =
C:\workspace\jakarta-hivemind/target/docs
[echo] | //uri to start crawling/generation process
[echo] | project.start-uri = linkmap.html
[echo] | //cocoon cli.xconf location
[echo] | project.configfile =
C:\workspace\jakarta-hivemind\ext-package\apache-forrest-0.6\src\core/context/WEB-INF/cli.xconf
[echo] | //logkit.xconf location
[echo] | project.logkitfile =
C:\workspace\jakarta-hivemind\ext-package\apache-forrest-0.6\src\core/context/WEB-INF/logkit.xconf
[echo] | //temp dir to throw stuff in (i.e. work and ctxt)
[echo] | project.temp-dir = target/forrest
[echo] | //temp working directory for generation process
[echo] | project.cocoon-work-dir =
C:\workspace\jakarta-hivemind\target\forrest\cocoon-work
[echo] | //temp context directory for generation process
[echo] | project.webapp =
C:\workspace\jakarta-hivemind\target\forrest\webapp
[echo] | //debuglevel for logging (DEBUG, INFO, WARN,
ERROR, FATAL_ERROR)
[echo] | project.debuglevel = DEBUG
[echo] | //file for list of broken links
[echo] | project.brokenlinkfile =
C:\workspace\jakarta-hivemind\target\forrest\brokenlinks.xml
[echo] | //check if you have tools.jar installed
[echo] | tools.jar.present = true
[echo] ------------------------------------------------
[echo] | The following properties could be removed from
future builds:
[echo] | //which skin to apply
[echo] | project.skin = pelt
[echo] | //where your documentation xml is
[echo] | project.content-dir =
C:\workspace\jakarta-hivemind\target\forrest-composite
[echo] ------------------------------------------------
check-skin:
fetch-skins-descriptors:
fetch-skin:
unpack-skins:
init-skins:
init:
-prepare-classpath:
check-contentdir:
examine-proj:
validation-props:
validate-xdocs:
Warning: catalogpath listing external catalogs will be ignored
BUILD FAILED
C:\workspace\jakarta-hivemind\build.xml:40: The following error
occurred while executing this line:
C:\workspace\jakarta-hivemind\hivebuild\forrestdoc.xml:18: The
following error occurred while executing this line:
C:\workspace\jakarta-hivemind\ext-package\apache-forrest-0.6\src\core\targets\validate.xml:143:
Could not validate document
C:\workspace\jakarta-hivemind\target\forrest-compos
ite\content\xdocs\tabs.xml
Total time: 3 minutes 33 seconds
bash-2.05b$
My tabs.xml is unchanged from before, and worked in Forrest 0.5:
<?xml version="1.0" encoding="UTF-8"?>
<!--
Copyright 2004 The Apache Software Foundation
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
-->
<!DOCTYPE tabs PUBLIC "-//APACHE//DTD Cocoon Documentation Tab
V1.0//EN" "http://apache.org/forrest/dtd/tab-cocoon-v10.dtd">
<tabs software="HiveMind"
title="HiveMind Project"
copyright="Apache Software Foundation"
xmlns:xlink="http://www.w3.org/1999/xlink">
<!-- The rules are:
@dir will always have '/@indexfile' added.
@indexfile gets appended to @dir if the tab is selected. Defaults
to 'index.html'
@href is not modified unless it is root-relative and obviously specifies a
directory (ends in '/'), in which case /index.html will be added
HLS NOTE: I don't think the following line is accurate!
If @id's are present, site.xml entries with a matching @tab will
be in that tab.
-->
<tab label="HiveMind Project" href="index.html" id="project"/>
<tab label="Module: hivemind" dir="hivemind" href="hivemind" id="hivemind"/>
<tab label="Module: hivemind-lib" dir="hivemind-lib"
href="hivemind-lib" id="hivemind-lib"/>
<tab label="Example Code" dir="hivemind-examples"
href="hivemind-examples" id="hivemind-examples"/>
</tabs>
On 19 Oct 2004 00:06:39 +1000, David Crossley <cr...@apache.org> wrote:
. . .
Re: Upgrade to 0.6: validation issues
Posted by David Crossley <cr...@apache.org>.
Howard Lewis Ship wrote:
<snip/>
>
> I have no idea what this build-info.xml file is about! This is not a
> useful error message for me, and leaves me at a loss as to how to
> proceed. Other than updating the PUBLIC IDs of my xml files, I've
> changed nothing else.
Other than hacking the build system and trying to "emulate"
it with your own :-)
Why not just follow the method described to use Ant <import> ?
http://forrest.apache.org/docs/upgrading_06.html#antproxy
It seems that your build system is banging stuff into
various places under $FORREST_HOME and then not being
able to find it. Why are you explicitly setting project.home
to some place underneath forrest.home?
Anyway, try the import task
--
David Crossley
Re: Upgrade to 0.6: validation issues
Posted by Howard Lewis Ship <hl...@gmail.com>.
I then modified my Ant script (it's vitally important to be able to
build from Ant):
<target name="run-forrest" description="Runs Forrest to generate
final site documentation.">
<announce message="Invoking Forrest ..."/>
<java classname="org.apache.tools.ant.Main" fork="true" dir="${basedir}">
<arg line="-emacs -buildfile ${forrest.home}/forrest.build.xml"/>
<sysproperty key="forrest.home" value="${forrest.home}"/>
<sysproperty key="project.home" value="${basedir}"/>
<classpath>
<fileset dir="${forrest.home}/../..">
<include name="lib/endorsed/*.jar"/>
<include name="tools/ant/lib/*.jar"/>
</fileset>
</classpath>
</java>
</target>
I'm trying to emulate what the forrest.bat script file would do. I'm
launching a new version of Ant, using the libraries packaged with
Forrest. This works better; it validates my XML files and appears to
use the local catalog ... but it doesn't build:
run-forrest:
[echo]
[echo]
[echo] *** Invoking Forrest ...
[echo]
[java] Buildfile:
C:\workspace\jakarta-hivemind\ext-package\apache-forrest-0.6\src\core\forrest.build.xml
[java] init-props:
[java] Loading project specific properties from
C:\workspace\jakarta-hivemind\forrest.properties
[java] Loading user specific properties from C:\Documents and
Settings\Howard\forrest.properties
[java] Loading default properties from
C:\workspace\jakarta-hivemind\ext-package\apache-forrest-0.6\src\core\context\default-forrest.properties
[java] echo-settings:
[java] ------------------------------------------------
[java] | Forrest template run.
[java] | Running from ${forrest.home} =
C:\workspace\jakarta-hivemind\ext-package\apache-forrest-0.6\src\core
[java] | Working on ${project.home} = C:\workspace\jakarta-hivemind
[java] ------------------------------------------------
[java] | //where to put the result
[java] | project.site-dir =
C:\workspace\jakarta-hivemind/target/docs
[java] | //uri to start crawling/generation process
[java] | project.start-uri = index.html
[java] | //cocoon cli.xconf location
[java] | project.configfile =
C:\workspace\jakarta-hivemind\ext-package\apache-forrest-0.6\src\core/context/WEB-INF/cli.xconf
[java] | //logkit.xconf location
[java] | project.logkitfile =
C:\workspace\jakarta-hivemind\ext-package\apache-forrest-0.6\src\core/context/WEB-INF/logkit.xconf
[java] | //temp dir to throw stuff in (i.e. work and ctxt)
[java] | project.temp-dir = target/forrest
[java] | //temp working directory for generation process
[java] | project.cocoon-work-dir =
C:\workspace\jakarta-hivemind\ext-package\apache-forrest-0.6\src\core\target\forrest\cocoon-work
[java] | //temp context directory for generation process
[java] | project.webapp =
C:\workspace\jakarta-hivemind\target\forrest\webapp
[java] | //debuglevel for logging (DEBUG, INFO, WARN,
ERROR, FATAL_ERROR)
[java] | project.debuglevel = DEBUG
[java] | //file for list of broken links
[java] | project.brokenlinkfile =
C:\workspace\jakarta-hivemind\ext-package\apache-forrest-0.6\src\core\target\forrest\brokenlinks.xml
[java] | //check if you have tools.jar installed
[java] | tools.jar.present = true
[java] ------------------------------------------------
[java] | The following properties could be removed from
future builds:
[java] | //which skin to apply
[java] | project.skin = pelt
[java] | //where your documentation xml is
[java] | project.content-dir =
C:\workspace\jakarta-hivemind\C:\workspace\jakarta-hivemind\target\forrest-composite
[java] ------------------------------------------------
[java] check-skin:
[java] fetch-skins-descriptors:
[java] fetch-skin:
[java] unpack-skins:
[java] init-skins:
[java] init:
[java] -prepare-classpath:
[java] check-contentdir:
[java] examine-proj:
[java] validation-props:
[java] validate-xdocs:
[java] validate-skinconf:
[java] validate-sitemap:
[java] validate-skins-stylesheets:
[java] validate-skins:
[java] validate-skinchoice:
[java] ...validated existence of skin 'pelt'
[java] validate-stylesheets:
[java] validate:
[java] site:
[java] BUILD SUCCESSFUL
[java] Total time: 2 seconds
BUILD SUCCESSFUL
Total time: 4 seconds
C:\workspace\jakarta-hivemind>ant fast-site
Buildfile: build.xml
copy-documentation-to-composite:
fast-site:
copy-documentation-to-composite:
copy-documentation-to-composite:
copy-documentation-to-composite:
run-forrest:
[echo]
[echo]
[echo] *** Invoking Forrest ...
[echo]
[java] Buildfile:
C:\workspace\jakarta-hivemind\ext-package\apache-forrest-0.6\src\core\forrest.build.xml
[java] init-props:
[java] Loading project specific properties from
C:\workspace\jakarta-hivemind\forrest.properties
[java] Loading user specific properties from C:\Documents and
Settings\Howard\forrest.properties
[java] Loading default properties from
C:\workspace\jakarta-hivemind\ext-package\apache-forrest-0.6\src\core\context\default-forrest.properties
[java] echo-settings:
[java] ------------------------------------------------
[java] | Forrest template run.
[java] | Running from ${forrest.home} =
C:\workspace\jakarta-hivemind\ext-package\apache-forrest-0.6\src\core
[java] | Working on ${project.home} = C:\workspace\jakarta-hivemind
[java] ------------------------------------------------
[java] | //where to put the result
[java] | project.site-dir =
C:\workspace\jakarta-hivemind/target/docs
[java] | //uri to start crawling/generation process
[java] | project.start-uri = linkmap.html
[java] | //cocoon cli.xconf location
[java] | project.configfile =
C:\workspace\jakarta-hivemind\ext-package\apache-forrest-0.6\src\core/context/WEB-INF/cli.xconf
[java] | //logkit.xconf location
[java] | project.logkitfile =
C:\workspace\jakarta-hivemind\ext-package\apache-forrest-0.6\src\core/context/WEB-INF/logkit.xconf
[java] | //temp dir to throw stuff in (i.e. work and ctxt)
[java] | project.temp-dir = target/forrest
[java] | //temp working directory for generation process
[java] | project.cocoon-work-dir =
C:\workspace\jakarta-hivemind\ext-package\apache-forrest-0.6\src\core\target\forrest\cocoon-work
[java] | //temp context directory for generation process
[java] | project.webapp =
C:\workspace\jakarta-hivemind\target\forrest\webapp
[java] | //debuglevel for logging (DEBUG, INFO, WARN,
ERROR, FATAL_ERROR)
[java] | project.debuglevel = DEBUG
[java] | //file for list of broken links
[java] | project.brokenlinkfile =
C:\workspace\jakarta-hivemind\ext-package\apache-forrest-0.6\src\core\target\forrest\brokenlinks.xml
[java] | //check if you have tools.jar installed
[java] | tools.jar.present = true
[java] ------------------------------------------------
[java] | The following properties could be removed from
future builds:
[java] | //which skin to apply
[java] | project.skin = pelt
[java] | //where your documentation xml is
[java] | project.content-dir =
C:\workspace\jakarta-hivemind\target\forrest-composite
[java] ------------------------------------------------
[java] check-skin:
[java] fetch-skins-descriptors:
[java] fetch-skin:
[java] unpack-skins:
[java] init-skins:
[java] init:
[java] -prepare-classpath:
[java] check-contentdir:
[java] examine-proj:
[java] validation-props:
[java] validate-xdocs:
[java] 45 file(s) have been successfully validated.
[java] ...validated xdocs
[java] validate-skinconf:
[java] 1 file(s) have been successfully validated.
[java] ...validated skinconf
[java] validate-sitemap:
[java] ...validated sitemap
[java] validate-skins-stylesheets:
[java] validate-skins:
[java] validate-skinchoice:
[java] ...validated existence of skin 'pelt'
[java] validate-stylesheets:
[java] validate:
[java] site:
[java] Deleting directory
C:\workspace\jakarta-hivemind\ext-package\apache-forrest-0.6\src\core\target\forrest\cocoon-work
[java] Created dir:
C:\workspace\jakarta-hivemind\ext-package\apache-forrest-0.6\src\core\target\forrest\cocoon-work
[java] Copying the various non-generated resources to site.
[java] Warnings will be issued if the optional project resources
are not found.
[java] This is often the case, because they are optional and so
may not be available.
[java] Copying project resources and images to site ...
[java] Warning:
C:\workspace\jakarta-hivemind\target\forrest\webapp\resources not
found.
[java] Copying 1 file to C:\workspace\jakarta-hivemind\target\docs
[java] Copying main skin images to site ...
[java] Copying 21 files to
C:\workspace\jakarta-hivemind\target\docs\skin\images
[java] Copying 13 files to
C:\workspace\jakarta-hivemind\target\docs\skin\images
[java] Copying project skin images to site ...
[java] Warning:
C:\workspace\jakarta-hivemind\ext-package\apache-forrest-0.6\src\core\target\forrest-composite\skins\common\images
not found.
[java] Warning:
C:\workspace\jakarta-hivemind\ext-package\apache-forrest-0.6\src\core\target\forrest-composite\skins\pelt\images
not found.
[java] Copying main skin css and js files to site ...
[java] Copying 8 files to C:\workspace\jakarta-hivemind\target\docs\skin
[java] Copying 6 files to C:\workspace\jakarta-hivemind\target\docs\skin
[java] Copying project skin css and js files to site ...
[java] Warning:
C:\workspace\jakarta-hivemind\ext-package\apache-forrest-0.6\src\core\target\forrest-composite\skins\common
not found.
[java] Warning:
C:\workspace\jakarta-hivemind\ext-package\apache-forrest-0.6\src\core\target\forrest-composite\skins\pelt
not found.
[java] Finished copying the non-generated resources.
[java] Now Cocoon will generate the rest ...
[java] Static site will be generated at:
[java] C:\workspace\jakarta-hivemind/target/docs
[java] Note that there are various reasons for "build failed" messages.
[java] * Cocoon will report the status of each document:
[java] - in column 1: *=okay X=brokenLink ^=pageSkipped (see FAQ).
[java] * Even if only one link is broken, you will still get "failed".
[java] * Your site would still be generated, but some pages would
be broken.
[java] * Please check the file:
[java] C:\workspace\jakarta-hivemind\ext-package\apache-forrest-0.6\src\core\target\forrest\brokenlinks.xml
[java] for any broken links in the generated site.
[java] ------------------------------------------------------------------------
[java] cocoon 2.2.0-dev
[java] Copyright (c) 1999-2004 Apache Software Foundation. All
rights reserved.
[java] ------------------------------------------------------------------------
[java] Cannot find CatalogManager.properties
[java] X [0] linkmap.html
BROKEN: C:\workspace\jakarta-hivemind\ext-package\apache-forrest-0.6\src\core\context\target\forrest\bu
ild-info.xml (The system cannot find the path specified)
[java] Total time: 0 minutes 5 seconds, Site size: 0 Site pages: 0
[java] BUILD FAILED
[java] C:\workspace\jakarta-hivemind\ext-package\apache-forrest-0.6\src\core\targets\site.xml:43:
Java returned: 1
[java] Total time: 20 seconds
[java] Java Result: 1
I have no idea what this build-info.xml file is about! This is not a
useful error message for me, and leaves me at a loss as to how to
proceed. Other than updating the PUBLIC IDs of my xml files, I've
changed nothing else.
Re: Upgrade to 0.6: validation issues
Posted by David Crossley <cr...@apache.org>.
Howard Lewis Ship wrote:
> I'm trying to upgrade to forrest 0.6.
>
> First off; I had to change all my v1.2 DTD to v1.3, i.e.
>
> <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.2//EN"
>
>
> to
> <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN"
>
>
> I would have through Forrest 0.6 would have been gracious enough to
> support v1.2?
Whoa, steady on. Don't leap to conclusions. We would not do that.
If you look at Forrest's own documentation you would see
than many of our docs still use v1.2
> Perhaps it is related to my second problem:
>
> Doesn't seem to be recognizing/using local catalogs and DTDs.
You would have done better to start with that simple statement.
> Thus I have to set my system identifier to
> "http://xml.apache.org/forrest/dtd/document-v13.dtd"
> for validation to work ... and validation is slow!
Of course. You now have network overheads.
> Here's how I run forrest:
>
> <property name="forrest-package-dir"
> value="${external.package.dir}/apache-forrest-0.6"/>
> <property name="forrest.home" location="${forrest-package-dir}/src/core"/>
> <import file="${forrest.home}/forrest.build.xml"/>
>
> <target name="run-forrest" description="Runs Forrest to generate
> final site documentation.">
> <announce message="Invoking Forrest ..."/>
>
> <antcall target="site.site"/>
>
> </target>
>
>
> Here's what it looks like at runtime:
>
> bash-2.05b$ ant fast-site
> Buildfile: build.xml
>
> copy-documentation-to-composite:
>
> fast-site:
>
> copy-documentation-to-composite:
>
> copy-documentation-to-composite:
>
> copy-documentation-to-composite:
>
> run-forrest:
> [echo]
> [echo]
> [echo] *** Invoking Forrest ...
> [echo]
>
> init-props:
> [echo] Loading project specific properties from
> C:\workspace\jakarta-hivemind\forrest.properties
> [echo] Loading user specific properties from C:\Documents and
> Settings\Howard\forrest.properties
> [echo] Loading default properties from
> C:\workspace\jakarta-hivemind\ext-package\apache-forrest-0.6\src\core\context\default-forrest.properties
>
> echo-settings:
> [echo] ------------------------------------------------
> [echo] | Forrest template run.
> [echo] | Running from ${forrest.home} =
> C:\workspace\jakarta-hivemind\ext-package\apache-forrest-0.6\src\core
> [echo] | Working on ${project.home} = C:\workspace\jakarta-hivemind
> [echo] ------------------------------------------------
> [echo] | //where to put the result
> [echo] | project.site-dir =
> C:\workspace\jakarta-hivemind/target/docs
> [echo] | //uri to start crawling/generation process
> [echo] | project.start-uri = linkmap.html
> [echo] | //cocoon cli.xconf location
> [echo] | project.configfile =
> C:\workspace\jakarta-hivemind\ext-package\apache-forrest-0.6\src\core/context/WEB-INF/cli.xconf
> [echo] | //logkit.xconf location
> [echo] | project.logkitfile =
> C:\workspace\jakarta-hivemind\ext-package\apache-forrest-0.6\src\core/context/WEB-INF/logkit.xconf
> [echo] | //temp dir to throw stuff in (i.e. work and ctxt)
> [echo] | project.temp-dir = target/forrest
> [echo] | //temp working directory for generation process
> [echo] | project.cocoon-work-dir =
> C:\workspace\jakarta-hivemind\target\forrest\cocoon-work
> [echo] | //temp context directory for generation process
> [echo] | project.webapp =
> C:\workspace\jakarta-hivemind\target\forrest\webapp
> [echo] | //debuglevel for logging (DEBUG, INFO, WARN,
> ERROR, FATAL_ERROR)
> [echo] | project.debuglevel = DEBUG
> [echo] | //file for list of broken links
> [echo] | project.brokenlinkfile =
> C:\workspace\jakarta-hivemind\target\forrest\brokenlinks.xml
> [echo] | //check if you have tools.jar installed
> [echo] | tools.jar.present = true
> [echo] ------------------------------------------------
> [echo] | The following properties could be removed from
> future builds:
> [echo] | //which skin to apply
> [echo] | project.skin = pelt
> [echo] | //where your documentation xml is
> [echo] | project.content-dir =
> C:\workspace\jakarta-hivemind\target\forrest-composite
> [echo] ------------------------------------------------
>
> check-skin:
>
> fetch-skins-descriptors:
>
> fetch-skin:
>
> unpack-skins:
>
> init-skins:
>
> init:
>
> -prepare-classpath:
>
> check-contentdir:
>
> examine-proj:
>
> validation-props:
>
> validate-xdocs:
> Warning: catalogpath listing external catalogs will be ignored
I think that this is because you are using your own version
of Ant to do Forrest's work. If you call 'forrest' with its
own shell script, then it uses its own packaged Ant and the
supporting catalog entity resolver. Because you are using your
own Ant you need to supply the entity resolver. I still need
to experiment with this myself, but try copying
forrest/lib/xml-commons-resolver-1.1.jar $ANT_HOME/lib
--
David Crossley