Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 47193 invoked from network); 2 Oct 2009 14:12:35 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 2 Oct 2009 14:12:35 -0000 Received: (qmail 98515 invoked by uid 500); 2 Oct 2009 14:12:35 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 98445 invoked by uid 500); 2 Oct 2009 14:12:35 -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 98437 invoked by uid 99); 2 Oct 2009 14:12:35 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Oct 2009 14:12:35 +0000 X-ASF-Spam-Status: No, hits=-4.0 required=10.0 tests=RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [192.18.6.24] (HELO gmp-eb-inf-2.sun.com) (192.18.6.24) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Oct 2009 14:12:23 +0000 Received: from fe-emea-09.sun.com (gmp-eb-lb-1-fe1.eu.sun.com [192.18.6.7] (may be forged)) by gmp-eb-inf-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id n92EC2bp019485 for ; Fri, 2 Oct 2009 14:12:02 GMT MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII; format=flowed Received: from conversion-daemon.fe-emea-09.sun.com by fe-emea-09.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) id <0KQW00G004AQD900@fe-emea-09.sun.com> for derby-dev@db.apache.org; Fri, 02 Oct 2009 15:11:41 +0100 (BST) Received: from [129.150.206.6] ([unknown] [129.150.206.6]) by fe-emea-09.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) with ESMTPSA id <0KQW007BT4RHXD20@fe-emea-09.sun.com> for derby-dev@db.apache.org; Fri, 02 Oct 2009 15:11:41 +0100 (BST) Date: Fri, 02 Oct 2009 16:11:25 +0200 From: Kristian Waagan Subject: Re: Apache Derby source code compilation probleme In-reply-to: <25715958.post@talk.nabble.com> Sender: Kristian.Waagan@Sun.COM To: derby-dev@db.apache.org Message-id: <4AC60A0D.2090301@Sun.COM> Organization: Sun Microsystems Inc. References: <25715958.post@talk.nabble.com> User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) X-Virus-Checked: Checked by ClamAV on apache.org bb00bbyy wrote: > Hi Apache Derby Developers, > > I'm currently working on a project ending my software engineering studies. > And I'm french so my english might not be perfect. > > So this is the probleme I've encountered during project building : > I got the Apache Derby source code from SVN, latest release 10.5.3. > And I follows every steps to build Derby (and configure Eclipse Ganymede > version). > When I run the build.xml in the root of the Apache Derby project, it writes > me that BUILD is SUCCESSFULL but eventually, I do not have in my folder any > JAR. And that's the matter 'cause I need to be able to modify the engine of > Apache Derby and to use the resulting "derby.jar". > > Actually, I need to improve the Apache Derby project to make it use some > kind of fuzzy queries. > And I must directly modify the engine to do this. But I can't compile and > get derby.jar. > > So I quickly read the build.xml file (14000 lines, I can't read all of it), > and I decide to run directly the target named "buildjars". It results in > creating a folder named "jars" containing all the JAR available in the > Apache_derby_bin.zip downloadable on the official web site. But when I make > some changes in the code and I rebuild (always using "buildjars" target > directly), it doesn't seem the derby.jar is different. > > So please can you help me with this ? > Hello, A shot in the dark to get you going: ant clobber all buildjars This will do the following; - clobber: will clean up any existing build artifacts (may not be needed all the time) - all: will compile the classes - buildjars: will generate the jar files (from the classes) Depending on what you're going to use the JARs for, you may want to configure the build to create either sane or insane code (with or without debug code). There should also be some information in 'BUILDING.html'. If this doesn't help, feel free to ask the list again :) Regards, -- Kristian > Thank you >