cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject Re: Re: installing and configuring cocoon 2.2
Date Tue, 27 Mar 2007 13:45:33 GMT
hi Grzegorz,

the way i described it works for me. i had a look at the document you 
posted in your reply. thats pretty much the way i do/did it (parent pom 
(entire project) and modules (part cocoon blocks, part libraries) ).
still the cocoon deployer plugin is used to deploy the cocoon blocks (i 
have several in the project) into a servlet container (jetty in 
development). it executes in the maven build-lifecycle phase "package" 
with the goal "deploy" for the cocoon blocks.
can't say for sure this is needed though.

Freundliche Grüße / With kind regards
Thomas Zirke

Klingenderstr. 5
D 33100 Paderborn

voice           +49 5251/1581-984
fax             +49 5251/1581-71

Klaus Beverungen
Josef Tillmann

Vorsitzender des Aufsichtsrates
Heinz-Dieter Wendorff

Amtsgericht Paderborn HRB 3270

Grzegorz Kossakowski <>
27.03.2007 15:15
Bitte antworten an users
        Thema:  Re: installing and configuring cocoon 2.2 napisał(a):
> hi bart,
> try the "tools/cocoon-block-deployer/cocoon-deployer-plugin-demo"
> sample (comes with Cocoon 2.2) . The pom.xml of that sample should
> include all information needed for deploying a Cocoon Block to run in
> a Servlet Container. Additionally you will have to configure your
> Application (pom.xml) to use all Cocoon Blocks required by your
> application (see dependency sample).
> <dependencies>
>         <dependency>
>                      <groupId>org.apache.cocoon</groupId>
>               <artifactId>cocoon-forms-impl</artifactId>
>                      <version>1.0.0-M2-SNAPSHOT</version>
>       </dependency>
>         <!--more dependencies here-->
> </dependencies>
> check the cocoon blocks (source) you wish to use and copy the
> dependency information from the respective blocks pom.xml. it would be
> wise to build cocoon 2.2 locally before trying to get your application
> to work. you can of cource do it without actually building cocoon but
> then you'll have to configure your applikation (pom.xml) to use at
> least one maven2 repository which supplies cocoon 2.2 artifacts. the
> latter alternative of course brings along the convenience of not
> having to build cocoon entirely or in part whenever some cocoon source
> changes, but to retrieve changed cocoon blocks via mavens dependency
> resolver.
> also check for more information on the use of
> maven2.
Hmm, to be honest, I do not understand what you suggest here. AFAIK,
cocoon-deployer-plugin is not needed and not developed anymore so is not
a good example. Why not using block/webapp archetypes as described here: ?

Grzegorz Kossakowski

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message