Return-Path: Delivered-To: apmail-jcp-open-archive@www.apache.org Received: (qmail 29681 invoked from network); 10 Aug 2006 21:26:06 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 10 Aug 2006 21:26:06 -0000 Received: (qmail 38474 invoked by uid 500); 10 Aug 2006 21:26:05 -0000 Delivered-To: apmail-jcp-open-archive@apache.org Received: (qmail 38413 invoked by uid 500); 10 Aug 2006 21:26:05 -0000 Mailing-List: contact jcp-open-help@apache.org; run by ezmlm Precedence: bulk Reply-To: jcp-open@apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list jcp-open@apache.org Delivered-To: moderator for jcp-open@apache.org Received: (qmail 53585 invoked by uid 99); 9 Aug 2006 22:39:09 -0000 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 david.blevins@visi.com designates 208.42.156.9 as permitted sender) Mime-Version: 1.0 (Apple Message framework v752.2) In-Reply-To: References: <4460E880.1090803@envoisolutions.com> <4460FAE9.6080209@apache.org> <4461063D.9040501@envoisolutions.com> <44616548.6080507@envoisolutions.com> <4461C01D.3070905@apache.org> <44D7903A.8080401@apache.org> <44D80CED.9040301@apache.org> <3A5A16B1-3A51-43E4-BEDC-E1C35D157CC6@SUN.com> <44D865F9.30602@apache.org> <44D91E14.2090403@apache.org> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: David Blevins Subject: Re: TCK agreement Date: Wed, 9 Aug 2006 15:38:42 -0700 To: jcp-open@apache.org X-Mailer: Apple Mail (2.752.2) X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N On Aug 8, 2006, at 5:18 PM, Craig L Russell wrote: > > I'd like to get a feel for how the others have set up the > repository. Is it up to each individual person to extract the tck, > create the source tree, set up run scripts, etc.? How much is > common to the project? On Geronimo, we had the TCK binary checked in as Geir mentions, but it made SVN cry, so we got rid of it. We still have an active geronimo-tck svn that contains lots of build files (maven 1), deployment descriptors, stuff for creating reports, and the results themselves. Basically, everything you need to run the tck and generate a report sans the tck binary itself. You can run pretty much any test with a single maven command. It definitely took us a while to build up that system. As lots of that stuff is largely tied to a specific Geronimo version (project.xml files, descriptors, results, etc.), we branch that content each time we branch Geronimo. Hope this helps. Happy to provide more info. -David