Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 88382 invoked from network); 20 Oct 2006 11:51:51 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 20 Oct 2006 11:51:51 -0000 Received: (qmail 94345 invoked by uid 500); 20 Oct 2006 11:51:51 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 94126 invoked by uid 500); 20 Oct 2006 11:51:50 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 94117 invoked by uid 99); 20 Oct 2006 11:51:50 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 20 Oct 2006 04:51:50 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=UNPARSEABLE_RELAY X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [192.18.1.36] (HELO gmp-ea-fw-1.sun.com) (192.18.1.36) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 20 Oct 2006 04:51:47 -0700 Received: from d1-emea-09.sun.com ([192.18.2.119]) by gmp-ea-fw-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id k9KBpL37025333 for ; Fri, 20 Oct 2006 12:51:26 +0100 (BST) Received: from conversion-daemon.d1-emea-09.sun.com by d1-emea-09.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) id <0J7F00401NDP5100@d1-emea-09.sun.com> (original mail from John.Embretsen@Sun.COM) for derby-dev@db.apache.org; Fri, 20 Oct 2006 12:51:21 +0100 (BST) Received: from [129.159.112.236] by d1-emea-09.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPSA id <0J7F00EGFNLLO8G9@d1-emea-09.sun.com> for derby-dev@db.apache.org; Fri, 20 Oct 2006 12:51:21 +0100 (BST) Date: Fri, 20 Oct 2006 13:49:02 +0200 From: John Embretsen Subject: Re: Derby source code... In-reply-to: Sender: John.Embretsen@Sun.COM To: derby-dev@db.apache.org Reply-to: derby-dev@db.apache.org Message-id: <4538B7AE.8000103@Sun.COM> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT References: User-Agent: Thunderbird 1.5.0.5 (X11/20060730) X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N ram wrote: > Hello!! > I am a newbie. > I am working on a project called "Concurrency Control And Locking > Protocol" in which we have to modify current source code of locking > protocol by a new locking protocol algorithm say SLP,designed by us to > test our SLP. Welcome to the Derby community! > Can anyone help me how and from where i can download derby source code? You can get most, if not all, the information you need from the Derby web site: http://db.apache.org/derby/ For information on Derby source code, click the "Download" tab and click on the link saying "Derby source code", or simply scroll down until you see it. > Where can i find Locking Protocol code and internals documentation of > derby source code? I'm sure it can be found by browsing the web site and/or using the search field on the left hand side. For example, under the "Resources tab" you will find a menu on the left pointing to "Papers". There you will find links to lots of info on Derby internals. The Apache Derby wiki may also contain some useful information, see http://wiki.apache.org/db-derby/ For new contributors, this page should be especially interesting: http://wiki.apache.org/db-derby/DerbyDev > After making some changes in derby source code i want to compile whole > source code to test new source code functionality?How can i compile and > test? Plz help me out.. This is described on the page that explains how to obtain Derby source code. In short, building is described in detail in BUILDING.txt (a file in the code repository), and (old-style) testing is described in java/testing/readme.htm. JUnit testing is described on the wiki at http://wiki.apache.org/db-derby/DerbyJUnitTesting. You may of course post questions to this mailing list if you have specific questions on Derby development. -- John