From dev-return-50043-apmail-geronimo-dev-archive=geronimo.apache.org@geronimo.apache.org Mon May 07 08:06:07 2007 Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 14913 invoked from network); 7 May 2007 08:06:06 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 7 May 2007 08:06:06 -0000 Received: (qmail 15608 invoked by uid 500); 7 May 2007 08:06:13 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 15056 invoked by uid 500); 7 May 2007 08:06:12 -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 15042 invoked by uid 99); 7 May 2007 08:06:12 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 07 May 2007 01:06:12 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: local policy) Received: from [68.142.206.241] (HELO smtp108.plus.mail.mud.yahoo.com) (68.142.206.241) by apache.org (qpsmtpd/0.29) with SMTP; Mon, 07 May 2007 01:06:04 -0700 Received: (qmail 37897 invoked from network); 7 May 2007 08:05:43 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Received:X-YMail-OSG:Mime-Version:In-Reply-To:References:Content-Type:Message-Id:Content-Transfer-Encoding:From:Subject:Date:To:X-Mailer; b=ujtvQuCopfjENRDgQ9KlcQfGoYCByXLr5qdMzEd3iZUPvI33ktabvMMVfjbExeJ/CM/vpqzcFq7qcZ+C/VKBcj+A8YNhGwUkYgGsQLc2UFLn713fY6xglK99FlcIOZoFN9G4Ra0IlvKc/4PlpUxIR237i4xDFiaYOd2Uuo5UAmw= ; Received: from unknown (HELO ?10.11.55.8?) (david_jencks@63.105.20.225 with plain) by smtp108.plus.mail.mud.yahoo.com with SMTP; 7 May 2007 08:05:43 -0000 X-YMail-OSG: nVpC26sVM1m639TL9RvIpT_vyQKY4q5ozuPP5_cJi7ib9Kj4SN3ntyh9kDV4Kv0nM4QyRula2OU1H05qPzGV9Tnpip6OVyfed9bEKe.yi0vzQX_MA9g- Mime-Version: 1.0 (Apple Message framework v752.3) In-Reply-To: <258569.60335.qm@web31706.mail.mud.yahoo.com> References: <258569.60335.qm@web31706.mail.mud.yahoo.com> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <3AC15C09-1CDE-4E60-8FA5-CB07D8EC9702@yahoo.com> Content-Transfer-Encoding: 7bit From: David Jencks Subject: Re: How do we build Geronimo? Date: Mon, 7 May 2007 01:05:31 -0700 To: dev@geronimo.apache.org X-Mailer: Apple Mail (2.752.3) X-Virus-Checked: Checked by ClamAV on apache.org I don't think anyone has a problem rebuilding geronimo as much as needed to pick up code changes for the tck. IIUC the automated tools jason is working on already do this. However there is some need in the tck framework to know how the server is laid out, for instance to install certificates in the correct location, and changing that will disrupt not only the tck scripting but many of our users. I kinda think that proposals to change the layout of the server should be discussed and voted on with a pretty large fraction of committers voting just to make sure that everyone is aware of what might change and has thought about it carefully. I'm afraid I haven't kept up with the changes that led to this discussion so I might be looking in the wrong direction. Just my thoughts david jencks On May 6, 2007, at 1:22 AM, Anita Kulshreshtha wrote: > Hi All, > We all have our own favorite way of building Geronimo. But how TCK > builds Geronimo affects us all. It would benefit us all to know how > the > incremental changes are built in TCK. It is reasonable to assume that > for every minor change TCK does/can not build from an empty .m2 > repo. I > am hoping that we can discuss answers to the folloing questions here > without disclosing anything covered under NDA. > 1. What steps are followed when geronimo-kernel or the jars in the lib > are modified? > 2. What steps are followed when a plugin is modified? > 3. What steps are followed when ge-activemq-ra.rar module is modified? > 4. Do we use mvn ( as opposed to mvn clean install) for assemblies? > 5. Do we depend on 'mvn clean' to delete the target directory when > building assemblies? > 6. Do we use a server image generated by an online build that did not > start with a clean .m2 repo? > 7. What steps are taken to ensure that the build does not download any > published (stale) geronimo SNAPSHOTs during an online build? > The way our build works, all changes (patches) are not created > equal. Some of them might need build instructions like build with > empty > repo, build with empty geronimo repo, clean assemblies, ensure local > geronimo artifacts etc.. I am hoping we can establish TCK build > guidelines for integrating various kinds of changes. > We could also categorize patches using 'degree of build' > required. It > would allow people working on TCK to ban certain kinds of changes > officially. For example they could say we are in ... phase and only > accepting changes below .... category. WDYT? > > Thanks > Anita > > > > > > ______________________________________________________________________ > ______________ > Get your own web address. > Have a HUGE year through Yahoo! Small Business. > http://smallbusiness.yahoo.com/domains/?p=BESTDEAL