[
https://issues.apache.org/jira/browse/COCOON-1898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12570496#action_12570496
]
Olivier Billard commented on COCOON-1898:
-----------------------------------------
Hi there,
This issue is quite old, and I also have the need of patching cocoon.xconf file
in a mavenized Cocoon 2.1.x application.
I have several jar artefacts corresponding to different possible configurations
(a base core, and customers-oriented/specific functionalities).
Is there any chance this would be managed ?
Thanks !
> [PATCH] XPatch support for maven-cocoon-deployer-plugin
> -------------------------------------------------------
>
> Key: COCOON-1898
> URL: https://issues.apache.org/jira/browse/COCOON-1898
> Project: Cocoon
> Issue Type: Improvement
> Components: - Build System: Maven
> Affects Versions: 2.2-dev (Current SVN)
> Reporter: Lars Trieloff
> Attachments: maven-cocoon-deployer-plugin-with-xpatch-support.patch
>
>
> The cocoon-deployer-plugin has currently no support for XPatch, which makes
> it difficult to modify the web.xml when developing cocoon blocks. For example
> the cocoon-xmldb-impl block should add, when deployed, a servlet for xindice
> and a servlet mapping for the xindice servlet. This was possible in 2.1 using
> the XConfToolTask, but is no longer possible with the current state of the
> deployer-plugin.
> My patch adds support for patching the web.xml file using *.xweb files in the
> /conf directory of a block by filtering the block's jar file during
> deployment for conf/*.xweb files, caching the patch document temporarily and
> applying them (using code from the orgiginal XConfToolTask in 2.1) to the
> web.xml. The patch has currently no support for other files than conf/*.xweb
> files and does not support any property expansion.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
