db-derby-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Db-derby Wiki] Update of "BuildingDerby" by jeanTanderson
Date Tue, 09 May 2006 17:49:07 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Db-derby Wiki" for change notification.

The following page has been changed by jeanTanderson:

The comment on the change is:
First cut&paste from old email, based on an IRC question on how to use Eclipse

New page:
'''Table of Contents'''

Feel free to add your tips for building Derby.

= Using Eclipse to Build Derby =

This information was resurrected from [http://mail-archives.apache.org/mod_mbox/db-derby-user/200501.mbox/%3c41EC110F.80000@bristowhill.com%3e
a really old email thread], so feel free to edit.

 1. Setup everything as per the Derby build doc "How to build Derby" 
section at http://db.apache.org/derby/derby_downloads.html. If 
you can build Derby from the command line, you're ready to set up Eclipse.

 1. Derby uses jdk14 and jdk13 for its builds. So using the default 
Eclipse building (which uses only one jdk ) may not a good idea.

   un-check the  Preferences for auto building.
   Window - Preferences - Workbench - Build automatically
   Window - Preferences - Run/Debug - Launching - Build (if required)
   before launching

 1. The rest of these instructions assume that you checked out the Derby 
10.1 codeline in this subdirectory:


   svn co 

 1. The Eclipse project workspace is pointed to C:\derby10_1,  if you try 
creating a project with the same name '10.1' as above Eclipse identifies 
the all the required subdirectories including the sources and the 
classes (will take some time) since the checked out Derby 10.1 has same 

 1. Setup Eclipse to recognize the 'classes' directory as the output folder.

   Right click on the build.xml (most external)  - Run  -  the first 'Ant
   Build' uses the default "buildsource"

   The second  'Ant Build'  gives you the choices of the ant target.

 1. The java executable that runs Ant from Eclipse needs to be able to 
find the JDK tools.jar file -- and it might not be able to find it if 
Ant is running from a JRE installation.

For the taglet build, Ant tries to pick tools.jar up from the JDK 
relative to the setting of the Java system property java.home, to avoid 
having to make a copy of the JDK's tools.jar to another location. On 
most systems, java.home is set to the *jre* directory of the JDK 
installation. So, relative to this directory, tools.jar is in 

However, if Ant is running from a JRE installation instead of a JDK 
installation, this directory will not exist.  If you add the -verbose 
property to the Ant command line (inside Eclipse) and capture the 
output, the 4th line of the output will give you the location of the 
java.home. Once you know the location of java.home, you can copy 
tools.jar to where the build expects it to be (${java.home}/../lib).

View raw message