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).
|