[
https://issues.apache.org/jira/browse/FOR-1091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12625018#action_12625018
]
David Crossley commented on FOR-1091:
-------------------------------------
The first step with synchronising our cocoon.xconf is to manually edit our
configuration. This was done by modifying our
$FORREST_HOME/main/webapp/WEB-INF/xconf/forrest-core.xconf in comparison with
the one generated by doing a build of Cocoon-2.1 configured for the blocks that
we use. Its build system assembles xconf stuff from cocoon core and relevant
blocks to generate $COCOON_HOME/build/webapp/WEB-INF/cocoon.xconf
This was done on 2008-08-21 (see r687944 to r688037).
Then the content of main/webapp/WEB-INF/xconf/forrest-core.xconf was added to
the actual xconf at main/webapp/WEB-INF/cocoon.xconf (in r688047). This latter
file will be used from here on. More synchronisation is needed, but now getting
close.
> review our cocoon.xconf for Cocoon-2.1 xconf and properties
> -----------------------------------------------------------
>
> Key: FOR-1091
> URL: https://issues.apache.org/jira/browse/FOR-1091
> Project: Forrest
> Issue Type: Task
> Components: Core operations
> Affects Versions: 0.9-dev
> Reporter: David Crossley
>
> In forrest/branches/update_cocoon_2.1.12-dev we need to review our
> main/webapp/WEB-INF/cocoon.xconf configuration and also our use of Cocoon
> properties.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
