Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 7364 invoked from network); 30 Jun 2006 18:01:05 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 30 Jun 2006 18:01:05 -0000 Received: (qmail 85723 invoked by uid 500); 30 Jun 2006 18:00:59 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 85667 invoked by uid 500); 30 Jun 2006 18:00:58 -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 85655 invoked by uid 99); 30 Jun 2006 18:00:58 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 30 Jun 2006 11:00:58 -0700 X-ASF-Spam-Status: No, hits=0.5 required=10.0 tests=DNS_FROM_RFC_ABUSE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of jason.dillon@gmail.com designates 64.233.184.230 as permitted sender) Received: from [64.233.184.230] (HELO wr-out-0506.google.com) (64.233.184.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 30 Jun 2006 11:00:57 -0700 Received: by wr-out-0506.google.com with SMTP id i12so361444wra for ; Fri, 30 Jun 2006 11:00:36 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:mime-version:in-reply-to:references:content-type:message-id:content-transfer-encoding:subject:date:to:x-mailer:from:sender; b=hJFb9X4UK0AtlQb/vQQ9DTjpM/gEjeC6La/mMuejHna+xYHcURvpblk0k7gSY8LXfZ/B2IlnhAtkH0mViNcc01xhZaGNLokz1oHXhB/NnYRDMXx5yssbjuQ4538lasuEjEEwmqT3IgURpPVhVKeTgfDL+Ik2rYwBR8CaZO0oy3A= Received: by 10.65.211.14 with SMTP id n14mr1285437qbq; Fri, 30 Jun 2006 11:00:36 -0700 (PDT) Received: from ?10.0.1.5? ( [67.180.143.96]) by mx.gmail.com with ESMTP id d2sm1214982qbc.2006.06.30.11.00.34; Fri, 30 Jun 2006 11:00:36 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v752.2) In-Reply-To: <20060630120937.72062.qmail@web31706.mail.mud.yahoo.com> References: <20060630120937.72062.qmail@web31706.mail.mud.yahoo.com> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit Subject: Re: M2 Issues and Actions Date: Fri, 30 Jun 2006 11:00:25 -0700 To: dev@geronimo.apache.org X-Mailer: Apple Mail (2.752.2) From: Jason Dillon Sender: Jason Dillon X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N >> While this may work most of the time, it is not ideal as when making >> changes to plugins, users will be mystified when those changes are >> not used on the first build. > > This is not true. The plugin is *not* used before it is built. The > problem is that maven does not even start the build until it has > downloaded all the plugins. Even a dummy plugin would work. Um... it is completely true. I am aware that the plugin is not used before it is built. BUT the point that I was making was that Maven must resolve the plugin before the build commences... that means that the plugin must exist in a repository (or cache) already, and that is the version that will be used for the current build cycle... NOT the plugin that will be compiled and installed as part of the current build. Therefor the current build will always use the version of the plugin that was built BEFORE the build started, NOT the version that is actually getting built. This is why I suggested that the plugin either be part of another project (detached from the main build) or as part of a bootstrap phase that is executed before the main build cycle. --jason