Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 80710 invoked from network); 28 Jul 2006 04:02:54 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 28 Jul 2006 04:02:54 -0000 Received: (qmail 70078 invoked by uid 500); 28 Jul 2006 04:02:52 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 70039 invoked by uid 500); 28 Jul 2006 04:02:52 -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 70028 invoked by uid 99); 28 Jul 2006 04:02:52 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 27 Jul 2006 21:02:52 -0700 X-ASF-Spam-Status: No, hits=4.5 required=10.0 tests=DATE_IN_PAST_24_48,DNS_FROM_RFC_ABUSE,DNS_FROM_RFC_POST,DNS_FROM_RFC_WHOIS,FORGED_YAHOO_RCVD X-Spam-Check-By: apache.org Received-SPF: neutral (asf.osuosl.org: local policy) Received: from [205.152.59.66] (HELO imf18aec.mail.bellsouth.net) (205.152.59.66) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 27 Jul 2006 21:02:48 -0700 Received: from ibm59aec.bellsouth.net ([74.237.109.96]) by imf18aec.mail.bellsouth.net with ESMTP id <20060728040227.YFTC10480.imf18aec.mail.bellsouth.net@ibm59aec.bellsouth.net> for ; Fri, 28 Jul 2006 00:02:27 -0400 Received: from [192.168.1.96] (really [74.237.109.96]) by ibm59aec.bellsouth.net with ESMTP id <20060728040227.PHWL19687.ibm59aec.bellsouth.net@[192.168.1.96]> for ; Fri, 28 Jul 2006 00:02:27 -0400 Mime-Version: 1.0 (Apple Message framework v749.3) In-Reply-To: <74e15baa0607251349v629c7dd8ta3f3362a2c818166@mail.gmail.com> References: <74e15baa0607251349v629c7dd8ta3f3362a2c818166@mail.gmail.com> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <6D5A55EB-75CF-4444-8386-60C7B4052713@yahoo.com> Content-Transfer-Encoding: 7bit From: David Jencks Subject: Re: Geronimo 1.1 JARs but not CARs on ibiblio; car-maven-plugin change Date: Wed, 26 Jul 2006 16:39:20 -0400 To: dev@geronimo.apache.org X-Mailer: Apple Mail (2.749.3) X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N You should be able to include a complete environment element in your plan and if you don't include any dependencies in your pom the plan processing mojo should do nothing. If this is not what happens please file a jira with details. thanks david jencks On Jul 25, 2006, at 4:49 PM, Aaron Mulder wrote: > So I can use Maven 2 against Geronimo 1.1 since the G 1.1 JARs have > been pushed to Maven 2. > > However, I can't use the car-maven-plugin to build a CAR in a script > the way we do in Geronimo because it appears that you're supposed to > list your parent module as a dependency, and none of the Geronimo 1.1 > CARs are in the Maven 2 repo. So you can list e.g. > geronimo/rmi-naming/1.1/car as a dependency if you want that to be > your parent, and the build dies with: > > [ERROR] BUILD ERROR > [INFO] > ---------------------------------------------------------------------- > -- > [INFO] Failed to resolve artifact. > > Missing: > ---------- > 1) geronimo:rmi-naming:car:1.1 > > I tried telling it to use version 1.0 just for grins, and it > downloaded an unbelievable amount of stuff -- and eventually died > here: > > Path to dependency: > 1) gplugins:quartz-scheduler-plugin:car:0.2.1 > 2) geronimo:rmi-naming:car:1.0 > 3) geronimo:geronimo-jetty:jar:1.0 > 4) org.springframework:spring:jar:1.2.5 > 5) org.springframework:spring-support:jar:1.2.5 > 6) javax.resource:connector:jar:1.0 > > This is pretty ridiculous, since the dependency is not actually needed > to build, we just want its name to write it into a plan file. I > originally was going to ask for the CARs to be posted, but not if is > has this side effect if pulling in an unholy amout of crap. > > I'd rather manually specify the in my plan and suppress > the "feature" that writes a modified into the target > plan. > > It looks like the offending code is in PlanProcessorMojo, so I'd like > to add a config option to that file to suppress the auto-generated > environment. But I don't know a whole lot about Maven plugins. Can > someone walk me through adding a config option to the car-maven-plugin > that will eventually be set into a variable on the PlanProcessorMojo > instance? > > Thanks, > Aaron