From dev-return-32800-apmail-geronimo-dev-archive=geronimo.apache.org@geronimo.apache.org Sat Jul 01 20:39:35 2006 Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 66740 invoked from network); 1 Jul 2006 20:39:33 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 1 Jul 2006 20:39:33 -0000 Received: (qmail 10777 invoked by uid 500); 1 Jul 2006 20:39:31 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 10733 invoked by uid 500); 1 Jul 2006 20:39:31 -0000 Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@geronimo.apache.org List-Id: Delivered-To: mailing list dev@geronimo.apache.org Received: (qmail 10722 invoked by uid 99); 1 Jul 2006 20:39:31 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 01 Jul 2006 13:39:31 -0700 X-ASF-Spam-Status: No, hits=1.4 required=10.0 tests=DNS_FROM_RFC_ABUSE,DNS_FROM_RFC_WHOIS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [68.142.201.181] (HELO web31701.mail.mud.yahoo.com) (68.142.201.181) by apache.org (qpsmtpd/0.29) with SMTP; Sat, 01 Jul 2006 13:39:30 -0700 Received: (qmail 88451 invoked by uid 60001); 1 Jul 2006 20:39:09 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=InR63oA9sTrKw2s4+GYG3M8Kb5jm90u0iWFPnqm4Fi3fmgqb3tD794mnVRmNqvx/7n9ushaBAWT/gGozet53XGGAd5mVFChe1ksvqJYukhO9ZCeni8+E7dNEx3LY4Hlfa9uWq2zVqIXBhL0KsZHgzN9PY0WrZyv2q9/4vBqYGT8= ; Message-ID: <20060701203909.88449.qmail@web31701.mail.mud.yahoo.com> Received: from [24.211.208.98] by web31701.mail.mud.yahoo.com via HTTP; Sat, 01 Jul 2006 13:39:09 PDT Date: Sat, 1 Jul 2006 13:39:09 -0700 (PDT) From: anita kulshreshtha Subject: Re: Assembling a Geronimo distribution in a m2 build - first look. To: dev@geronimo.apache.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N We can exclude META-INF/maven/.... from the jars by configuring the jar plugin to use false. I have not used it, but it should work. Thanks Anita --- Prasad Kashyap wrote: > The m-a-p is invoked twice for the following reasons: > > When we copy some modules into a m2 repo structure format, it also > copies the META-INF/maven/.. directories. This unneccesary directory > introduces a very long path too. So in the first execution, we use > the > to skip the archive process. In the second > execution, we copy over the repo structure from the staging area but > exclude the META-INF/maven dirs into our geronimo/repository. > > > We are unpacking scripts in the first execution. I think it's > redundant. I'll remove it. > > Cheers > Prasad > > > > On 7/1/06, Jason Dillon wrote: > > Why do we need to invoke the assembly plugin twice? It does not > look > > like there is anything in the steps you listed below that actually > > requires that the assembly plugin be invoked twice. Maybe I am > > wrong, can you shed some light on this please? > > > > --jason > > > > > > > Here's how we assemble our binaries > > > > > > 1. Our pom.xml first lists all and only geronimo modules, configs > and > > > apps as dependencies. The transitive deps are taken care of by > m-a-p. > > > > > > 2. We first invoke the geronimo-assembly-plugin's "installConfig" > goal > > > to install the configs into target/archive-temp/repository. This > mojo > > > will try to install all dependencies of type "car" when no > artifact is > > > explicitly specified. Since we have listed all configs as deps in > our > > > j2ee-jetty-server pom.xml, they are installed. > > > > > > 3. Then we invoke m-a-p with assembly descriptor setup.xml and > > > intermediaryAssembly set to true. The intermediaryAssembly set > to > > > true will create the staging area but skip the final archive > creation. > > > The setup.xml will copy all deps other than the from > > > localRepository to target/archive-temp/repository. We exclude the > > > configs here b'coz the configs are installed in step 2 above. So > now > > > we have the modules and the configs all in the same repo. > > > > > > 4. We also use this setup.xml to unpack the scripts module into > the > > > staging area. > > > > > > 5. Then we invoke m-a-p again with assembly descriptor bin.xml. > The > > > plugin copies the library jars, the schema files, the jars for > bin > > > etc. The *.bat and *.sh files that we copied into the staging > area in > > > step 4 are now bundled into the archive but with correct mode and > > > lineendings.. > > > > > > That's about it. > > > > > > Cheers > > > Prasad > > > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com