From dev-return-32767-apmail-geronimo-dev-archive=geronimo.apache.org@geronimo.apache.org Sat Jul 01 10:04:18 2006 Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 72893 invoked from network); 1 Jul 2006 10:04:17 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 1 Jul 2006 10:04:17 -0000 Received: (qmail 6981 invoked by uid 500); 1 Jul 2006 10:04:11 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 6941 invoked by uid 500); 1 Jul 2006 10:04:10 -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 6928 invoked by uid 99); 1 Jul 2006 10:04:10 -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 03:04:10 -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 66.249.82.198 as permitted sender) Received: from [66.249.82.198] (HELO wx-out-0102.google.com) (66.249.82.198) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 01 Jul 2006 03:04:09 -0700 Received: by wx-out-0102.google.com with SMTP id h30so332711wxd for ; Sat, 01 Jul 2006 03:03:48 -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=TkfhHjYY+8AADAM2oQjf7Lu6PyEyHED5sWm9bTc8UvD1E6EU75pm/2a/cnFFTNBR9ipQiasUahvF5q97mNjEpOJnO4HEXSO7OthCFK2gwN9BuwKH71dDfvh/FxxYR65TJVzRIO0EDYUNK6xkXfBpQrRuZsevemFqtFg4BGb3DiA= Received: by 10.70.92.2 with SMTP id p2mr2195759wxb; Sat, 01 Jul 2006 03:03:48 -0700 (PDT) Received: from ?10.0.1.5? ( [67.180.143.96]) by mx.gmail.com with ESMTP id i20sm2723537wxd.2006.07.01.03.03.46; Sat, 01 Jul 2006 03:03:48 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v752.2) In-Reply-To: <74e15baa0607010258l3f2be81dm9dc7c81670d06019@mail.gmail.com> References: <20060630120937.72062.qmail@web31706.mail.mud.yahoo.com> <74e15baa0607010258l3f2be81dm9dc7c81670d06019@mail.gmail.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: Sat, 1 Jul 2006 03:03:23 -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 Sure, I was going to add that, as well as update the README.txt... pending approval of the changes. That script would just facilitate the multi-stage build... and is not intended to be a replacement for invoking mvn directly. BUT, we can use build[.bat] to provide users with a one command method to execute a full build. --jason On Jul 1, 2006, at 2:58 AM, Aaron Mulder wrote: > Call me crazy, but cant we have a build.bat and build.sh in the root > directory that executes the multi-stage builds (modules, plugins, > OpenEJB if present, apps, assemblies, etc.)? > > Thanks, > Aaron > > On 6/30/06, Jason Dillon wrote: >> I also think we need another pre-stage that will build a few tiny >> extensions used by the other stages. Specifically a test-config >> module that sets up a common log4j.properties that is used by all >> tests. When we get a site build running then we also will need >> something similar for clover and checkstyle and other plugins. >> >> NOTE: This can be a pre-stage or can be the start of the separate >> build-support (or whatever we call it) tree, which will contain the >> standalone plugins and other modules that our builds need to >> function. >> >> --jason >> >> >> > So, my proposed build procedure: >> > >> > build modules + plugins >> > go somewhere else and build openejb >> > build apps + configs + assemblies >> > >> > The proposal of using snapshots of openejb from a repo prevents you >> > from doing a clean build and finding out that in fact you created a >> > problem in either openejb or configs/assembly. >> > >> > This 3 step process will prevent us from interspersing the modules >> > and configs builds which might be highly desirable to make our >> > dependency tracking the same as the maven dependency tracking. >> > Cant get everything :-( >> > >> > thanks >> > david jencks >> > >> >> >> >> --jason >> >> >> >> >> > >> >>