[ http://issues.apache.org/jira/browse/FOR-300?page=all ]
David Crossley resolved FOR-300:
--------------------------------
Fix Version: 0.8-dev
Resolution: Incomplete
Either the "destdir" element and the "dest" attribute of the "uri" element can
be used to specify the destination of the generated files. They are both
relative to the webapp directory.
We now use the uri/@dest (with a hard-code relative path) in our
site-author/conf/cli.xconf file to handle the mirrors.html generated file. We
also have an entry (with no label) in our site.xml file. So we have workarounds.
> using cli.xconf to add extra URIs for processing, docs generated in wrong
> place
> -------------------------------------------------------------------------------
>
> Key: FOR-300
> URL: http://issues.apache.org/jira/browse/FOR-300
> Project: Forrest
> Type: Bug
> Components: Launch 'forrest'
> Versions: 0.6, 0.7, 0.8-dev
> Reporter: David Crossley
> Fix For: 0.8-dev
>
> Using the Cocoon cli.xconf enables additional files to be scheduled for
> processing which are not declared in site.xml nor linked from any other
> documents. However, the generated files end up at $FORREST_HOME/site/ rather
> than in the project space at ./build/site/
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
