From dev-return-27762-apmail-geronimo-dev-archive=geronimo.apache.org@geronimo.apache.org Mon Apr 10 16:19:11 2006 Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 90379 invoked from network); 10 Apr 2006 16:19:10 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 10 Apr 2006 16:19:10 -0000 Received: (qmail 62742 invoked by uid 500); 10 Apr 2006 16:19:06 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 62686 invoked by uid 500); 10 Apr 2006 16:19:06 -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 62675 invoked by uid 99); 10 Apr 2006 16:19:06 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Apr 2006 09:19:06 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of goyathlay.geronimo@gmail.com designates 64.233.166.176 as permitted sender) Received: from [64.233.166.176] (HELO pproxy.gmail.com) (64.233.166.176) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Apr 2006 09:19:05 -0700 Received: by pproxy.gmail.com with SMTP id t32so1105958pyc for ; Mon, 10 Apr 2006 09:18:44 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=CcAXHKJEo+cydw1yFNdMUbsUtAwU2TdAohvU9i1bYJP7XoCHRNyU5AJZ4mdSQP/TA9CB8VBKeUQUOX5bFNnK//J/Tf6Wd3rByDUnhb/WusauOF/YH1/Np/LJzbUAEc7zZxety0+kCxE9uwFXkWoZaWmo03MymZ26oDeWv6viq8A= Received: by 10.35.88.17 with SMTP id q17mr1662058pyl; Mon, 10 Apr 2006 09:18:44 -0700 (PDT) Received: by 10.35.34.5 with HTTP; Mon, 10 Apr 2006 09:18:44 -0700 (PDT) Message-ID: Date: Mon, 10 Apr 2006 12:18:44 -0400 From: "Prasad Kashyap" To: dev@geronimo.apache.org, jacek@laskowski.net.pl Subject: Re: Questions about the packaging plugin In-Reply-To: <1b5bfeb50604090236s2190ab89xadec374ba82c478c@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <3ECAD913-C985-44E4-B433-7F9D299AACF2@iq80.com> <20060406145844.69228.qmail@web31701.mail.mud.yahoo.com> <1b5bfeb50604090236s2190ab89xadec374ba82c478c@mail.gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N I have used the "provided" scope in almost all the application poms. The scope prevents from bundling all dependencies jars from the pom into app's WEB-INF/lib. Only those jars that are really needed to be bundled are explictly specified in the pom with no scope element set. Cheers Prasad On 4/9/06, Jacek Laskowski wrote: > On 4/6/06, anita kulshreshtha wrote: > > Dain, > > Thanks! I need to sort out the dependencies anyway. IIUC, currently > > we are including the dependencies referenced by the plans, i.e. the > > ones needed by GBeans. We are including few extra ones. The maven > > transitive dependency list is very large compared to what we add > > currently. I think we should only add the dependencies needed for the > > GBeans.For example if we have a GBean : > > > class=3D"org.apache.geronimo.kernel.config.EditableConfigurationManager= Impl"> > > we should add geronimo-kernel as a dependency. > > Hi, > > I don't know whether it works or not, but I've come up with a weird > idea. I've been struggling with it for a while and since I could not > yet test it out I'll describe it here. > > The idea boils down to using the scope - provided - for all our > modules' dependencies. I do mean 'all'. As transitive dependency > mechanism doesn't apply in this case (when the scope is 'provided'), > it sets up Maven2 not to download other transitive dependencies and it > *might* mimic the work of M1 that only downloads the dependencies > listed in the pom (project.xml). We could list all of the dependencies > in the parent pom as compile (default) and override some in the > modules. > > The caveat is that we will likely duplicate/do the work Maven2 could > do for us, i.e. maintain the transitive dependencies, but once we have > migrated to M2, we could think about it again how to work it out. It's > a kind of a workaround to finish the migration. > > Does it really seem to be 'weird'? Could it work? > > > Anita > > Jacek > > -- > Jacek Laskowski > http://www.laskowski.org.pl >