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 18:07:49 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:
http://wiki.apache.org/db-derby/BuildingDerby

The comment on the change is:
MoinMoin formatting

------------------------------------------------------------------------------
  '''Table of Contents'''
  [[TableOfContents(2)]]
  
- Feel free to add your tips for building Derby.
+ Feel free to add your tips for building Derby below.
  
  = Using Eclipse to Build Derby =
  [[Anchor(UsingEclipseToBuildDerby)]]
  
- 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.
+ 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 update it.
  
+  1. Verify you can build Derby from the command line.
-  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.
  
+    Setup everything as per the Derby build doc "How to build Derby" 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.
  
+  1. Derby uses jdk14 and jdk13 for its builds. 
+ 
+    Using the default Eclipse building (which uses only one jdk ) may not a good idea.
+ 
-    un-check the  Preferences for auto building.
+   un-check the  Preferences for auto building.
     Window - Preferences - Workbench - Build automatically
     Window - Preferences - Run/Debug - Launching - Build (if required)
     before launching
  
+  1. Check out the Derby codeline
-  1. The rest of these instructions assume that you checked out the Derby 
- 10.1 codeline in this subdirectory:
  
+    The rest of these instructions assume that you checked out the Derby 10.1 codeline in
the subdirectory
-    C:\derby10_1\10.1
+    {{{C:\derby10_1\10.1}}}:
  
-    svn co 
- http://svn.apache.org/repos/asf/db/derby/code/branches/10.1/
+    {{{svn co http://svn.apache.org/repos/asf/db/derby/code/branches/10.1/}}}
  
-  1. The Eclipse project workspace is pointed to C:\derby10_1,  if you try 
+  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 name.
- 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 
- name.
  
   1. Setup Eclipse to recognize the 'classes' directory as the output folder.
  
@@ -43, +41 @@

  
     The second  'Ant Build'  gives you the choices of the ant target.
  
+  1. Find JDK tools.jar 
-  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.
  
+    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 
- ${java.home}/../lib/tools.jar.
  
+    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 {{{${java.home}/../lib/tools.jar}}}.
- 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).
  
+    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}}}).
+ 

Mime
View raw message