You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by Michael Wechner <mi...@wyona.com> on 2005/12/20 21:10:26 UTC
Re: working with custom blocks
Upayavira wrote:
>Michael Wechner wrote:
>
>
>>Hi
>>
>>I have created my own block for Cocoon-2.1.X, but realized that I have
>>to patch the following files:
>>
>>gump.xml and lib/jars.xml
>>
>>and also have to copy libs to lib/optional
>>
>>
>>Is there a way that one does not have to patch these files? Or am I
>>missing something?
>>
>>
>
>No. Now do you see why we need a decent blocks system in 2.2? :-)
>
>Actually, you can copy your jars into lib/local
>
that doesn't seem to work if the block contains Java sources
based on such a library
>and I believe they'll
>get copied into the WEB-INF/lib. You probably don't then need to edit
>jars.xml.
>
well, if one copies the library into lib/optional, then one
needs to edit jars.xml. I guess I will write a little ant process
to automate "patching" ;-)
Thanks
Michi
> But gump.xml will need to be updated if you want your block to
>be built by Cocoon's build process.
>
>Regards, Upayavira
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
>For additional commands, e-mail: users-help@cocoon.apache.org
>
>
>
>
--
Michael Wechner
Wyona - Open Source Content Management - Apache Lenya
http://www.wyona.com http://lenya.apache.org
michael.wechner@wyona.com michi@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org