cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Leszek Gawron (JIRA)" <>
Subject [jira] Commented: (COCOON-1898) [PATCH] XPatch support for maven-cocoon-deployer-plugin
Date Sun, 03 Sep 2006 19:31:23 GMT
    [ ] 
Leszek Gawron commented on COCOON-1898:

This would probably be a good idea if cocoon:deploy had no xpatching abilities. A separate
XPatch/XUpdate plugin could be fired.
The only thing I really dislike is the probable command line:

mvn clean war:exploded cocoon:deploy cocoon:xupdate jetty:run -o -Dmaven.test.skip=true

couldn't we make it any shorter. Isn't there any way to have only:
mvn clean cocoon:build jetty:run?

I do not want to have cocoon war'ed or installed into local repository also. That means copying
lots of MBytes on my slow laptop's drive.

Please advise.

> [PATCH] XPatch support for maven-cocoon-deployer-plugin
> -------------------------------------------------------
>                 Key: COCOON-1898
>                 URL:
>             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.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message