Return-Path: Delivered-To: apmail-cocoon-users-archive@www.apache.org Received: (qmail 72314 invoked from network); 27 Mar 2007 13:45:43 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 27 Mar 2007 13:45:43 -0000 Received: (qmail 81503 invoked by uid 500); 27 Mar 2007 13:45:46 -0000 Delivered-To: apmail-cocoon-users-archive@cocoon.apache.org Received: (qmail 81454 invoked by uid 500); 27 Mar 2007 13:45:46 -0000 Mailing-List: contact users-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: users@cocoon.apache.org List-Id: Delivered-To: mailing list users@cocoon.apache.org Received: (qmail 81439 invoked by uid 99); 27 Mar 2007 13:45:46 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 27 Mar 2007 06:45:46 -0700 X-ASF-Spam-Status: No, hits=2.5 required=10.0 tests=HTML_MESSAGE,NO_REAL_NAME X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: local policy) Received: from [212.8.217.2] (HELO mail.s-und-n.de) (212.8.217.2) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 27 Mar 2007 06:45:38 -0700 Received: from notes.sundn.de (ntsrv5.sundn.de [10.10.2.10]) by mail.s-und-n.de (postfix) with ESMTP id 49E8519FFB8 for ; Tue, 27 Mar 2007 15:45:13 +0200 (CEST) In-Reply-To: <460918D6.8060105@apache.org> To: users@cocoon.apache.org Subject: Re: Re: installing and configuring cocoon 2.2 MIME-Version: 1.0 X-Mailer: Lotus Notes Release 6.5 September 26, 2003 From: tzirke@s-und-n.de Message-ID: Date: Tue, 27 Mar 2007 15:45:33 +0200 X-MIMETrack: Serialize by Router on PBSN1/Systeme und Netzwerke(Release 6.5.3|September 14, 2004) at 27.03.2007 15:45:34, Serialize complete at 27.03.2007 15:45:34 Content-Type: multipart/alternative; boundary="=_alternative 004B57A5C12572AB_=" X-Virus-Checked: Checked by ClamAV on apache.org --=_alternative 004B57A5C12572AB_= Content-Type: text/plain; charset="ISO-8859-2" Content-Transfer-Encoding: quoted-printable hi Grzegorz, the way i described it works for me. i had a look at the document you=20 posted in your reply. thats pretty much the way i do/did it (parent pom=20 (entire project) and modules (part cocoon blocks, part libraries) ). still the cocoon deployer plugin is used to deploy the cocoon blocks (i=20 have several in the project) into a servlet container (jetty in=20 development). it executes in the maven build-lifecycle phase "package"=20 with the goal "deploy" for the cocoon blocks. can't say for sure this is needed though. Freundliche Gr=FC=DFe / With kind regards Thomas Zirke S&N AG Klingenderstr. 5 D 33100 Paderborn voice +49 5251/1581-984 fax +49 5251/1581-71 eMail tzirke@s-und-n.de Web http://www.s-und-n.de Vorstand Klaus Beverungen Josef Tillmann Vorsitzender des Aufsichtsrates Heinz-Dieter Wendorff Handelsregister Amtsgericht Paderborn HRB 3270 Grzegorz Kossakowski 27.03.2007 15:15 Bitte antworten an users =20 An: users@cocoon.apache.org Kopie:=20 Thema: Re: installing and configuring cocoon 2.2 tzirke@s-und-n.de napisa=B3(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). > > > > org.apache.cocoon > cocoon-forms-impl > 1.0.0-M2-SNAPSHOT > > > > > 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 http://maven.apache.org 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: http://cocoon.zones.apache.org/daisy/cdocs-site-main/g2/1159.html ? --=20 Grzegorz Kossakowski http://reflectingonthevicissitudes.wordpress.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org For additional commands, e-mail: users-help@cocoon.apache.org --=_alternative 004B57A5C12572AB_= Content-Type: text/html; charset="ISO-8859-2" Content-Transfer-Encoding: quoted-printable
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-li= fecycle phase "package" with the goal "deploy" for the cocoon blocks.
can't say for sure this is needed th= ough.

Freundliche Gr=FC=DFe / With kind re= gards
Thomas Zirke

S&N AG
Klingenderstr. 5
D 33100 Paderborn

voice +49 5251/1581-984
fax +49 5251/1581-71
eMail tzirke@s-und-n= .de
Web http://www.s-und= -n.de

Vorstand
Klaus Beverungen
Josef Tillmann

Vorsitzender des Aufsichtsrates
Heinz-Dieter Wendorff

Handelsregister
Amtsgericht Paderborn HRB 3270

Grzegorz Kossakowski <gkossako= wski@apache.org>

27.03.2007 15:15
Bitte antworten an users

An: users@cocoon.apache.org
Kopie:
Thema: Re: installing and configuring cocoon 2.2

tzirke@s-und-n.de napisa=B3(a): > > hi bart, > > try the "tools/cocoon-block-deployer/cocoon-deployer-plugin-demo&= quot; > 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>coc= oon-forms-impl</artifactId> > <version>1.0.0-M2-SNAPSHOT</version> > </dependency> >  > </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 http://maven.apache.org 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: http://cocoon.zones.apache.org/daisy/cdocs-site-main/g2/1159.html ? -- Grzegorz Kossakowski http://reflectingonthevicissitudes.wordpress.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org For additional commands, e-mail: users-help@cocoon.apache.org
--=_alternative 004B57A5C12572AB_=--