+Before building Derby, you need to download the following:
+
+
+
+
+
+
+
Prerequisite
+
Description
+
+
+
+
Derby Source
+
+If you are reading these instructions, chances
+ are you have already unpacked a Derby source distribution. However,
+ if you don't have the Derby source yet, get the development source tree from subversion by following these
+ instructions.
+
+
+
+
+
Java Development Kit
+
You need to install a Java 5 or later JDK. Probably, your machine
+ already has this JDK. If not, Sun and IBM supply free Java
+ 5 JDKs for many machines.
+
+
+
+
Ant
+
You need to install the Ant build tool, version 1.7.0 or
+ higher. You can get Ant here.
+
+
+
+
+
+
+
+
+If you are going to run the Derby tests, then you will need to download the JUnit
+test harness also:
+
+
+
+
+
+
+
Prerequisite
+
Description
+
+
+
+
JUnit
+
You need the JUnit test tool, version 3.8.1.
+ You can get JUnit 3.8.1 here.
+ Copy junit.jar jar into your Derby source tree, in the
+ tools/java directory.
+
+Before building Derby, cd
+to the root of your Derby source distribution. That is the top level
+directory which contains the LICENSE and NOTICE files. In addition,
+make sure that the version of Java which you are using is Java 5 or
+later. You can verify this by checking the output of the following command:
+
+
+
+
+java -version
+
+
+
+
+Now use the following Ant targets to build Derby.:
+
+
+
+
+
+
+
Target
+
Description
+
Command
+
+
+
+
clobber
+
This target deletes all build artifacts.
+
+
+
+ant -quiet clobber
+
+
+
+
+
+
+
buildsource
+
This target compiles all source files needed for the Derby
+ product. Don't be alarmed by all of the compiler warnings. We'll
+ show you how to tidy those up later on.
+
+If you want to build and run the Derby tests, make sure that you have downloaded
+the
+JUnit
+test framework. Then build all of the Derby sources, including the test classes:
+
+
+
+
+
+
+
Target
+
Description
+
Command
+
+
+
+
all
+
This target compiles all Derby source files.
+
+
+
+ant -quiet all
+
+
+
+
+
+
+
+
+
+Putting all of this together, here's how you build the tests:
+
+
+
+
+ant -quiet clobber
+ant -quiet all
+ant -quiet buildjars
+
+You can customize the Derby build by setting variables in a file
+called ant.properties. The Ant tool looks for this file in your
+home directory. To find out where Ant thinks your home directory is,
+issue the following command and look for "user.home" in the output:
+
+
+
+
+ant -diagnostics
+
+
+
+
+
+Here are some Derby-specific variables which you may want to set in ant.properties:
+
+
+
+
+
+
+
Variable
+
Description
+
Default
+
Example
+
+
+
+
deprecation
+
Turn this flag off if you don't want to see pages of
+ warnings generated when the compiler encounters references to
+ deprecated methods.
+
on
+
+
+
+deprecation=off
+
+
+
+
+
+
+
sane
+
By default, this variable is set to true. This builds
+ extra assertion and debugging logic into Derby classes. If you
+ set this variable to false, then the Derby jar files will be
+ smaller and Derby will run faster. During typical development,
+ you will leave this variable set to true. However, this
+ variable is set to false when building official Derby releases.
+Derby is supposed to run in all of the following environments:
+
+
+
+
+
+
+
Platform
+
JDBC Level
+
+
+
+
Java 6
+
JDBC 4
+
+
+
+
Java 5
+
JDBC 3
+
+
+
+
JDK 1.4.2
+
JDBC 3
+
+
+
+
Small Device (CDC/FP 1.1)
+
JSR169
+
+
+
+
+
+
+
+The default Derby build does NOT necessarily verify that the compile-time contract is
+satisifed for any of these platforms. To get compile-time checks, you
+need to make sure that the following variables are set correctly. To
+see the values which the Derby build uses for these variables, build
+Derby after setting the
+following debug variable in your ant.properties:
+
+
+
+
+printCompilerProperties=true
+
+
+
+
+
+Here are the variables which determine whether the Derby build
+enforces compile-time contracts for the supported platforms:
+
+
+
+
+
+
+
Platform
+
Compiler Variable
+
Description
+
Default Value
+
+
+
+
Java 6
+
java16compile.classpath
+
If you have a Java 6 JDK on your machine, this should be the list of all the
+ Java 6 jars. Sun and IBM provide free Java 6 JDKs for many machines.
+
classes/stubs/jdbc4:${java15compile.classpath}
+
+
+
+
Java 5
+
java15compile.classpath
+
The Derby build tries to find a Java 5
+ JDK on your machine. The build fails if it can't find this JDK.
+
The jars in your Java 5 JDK.
+
+
+
+
JDK 1.4.2
+
java14compile.classpath
+
The Derby build tries to find a 1.4 JDK
+ on your machine. If the build finds that JDK, then this
+ variable is set to the list of jars there. Again, Sun and IBM supply free 1.4.2 JDKs for many machines.
+
The list of jars in your 1.4 JDK if the build can find
+ them. Otherwise,
+ ${java15compile.classpath}:tools/java/xalan.jar:tools/java/serializer.jar
+
+
+
+
+
Small Device (CDC/FP 1.1)
+
jsr169compile.classpath
+
This should be set to the list of small device libraries on
+ your machine--if you have them. That is, the CDC/FP 1.1 jars and
+ the jsr169 jar. To get a set of small device libraries, see
+ Sun's instructions
+ or download IBM's WCTME 5.7.
+
+
classes/stubs/jsr169:${java14compile.classpath}
+
+
+
+
+
+
+The preceding variables are mandatory for the Derby build.
+For Mac OS X, Solaris, and many Linux and IBM machines, Derby
+can figure out where the JDKs live and can therefore set the
+preceding variables to reasonable values if you don't set them. For
+other platforms, the Derby build may not be able to figure out where the JDKs
+live. You can help the Derby build by setting the following optional
+variables in ant.properties:
+
+
+
+
+
+
+
Compiler Variable
+
Description
+
Default Value
+
+
+
+
j14lib
+
If you set this variable to be the directory which contains
+ your 1.4 jars, then the Derby build will set
+ java14compile.classpath to be the list of jars in that directory.
+
+
Optional variable. No default value.
+
+
+
+
j145ib
+
If you set this variable to be the directory which contains
+ your Java 5 jars, then the Derby build will set
+ java15compile.classpath to be the list of jars in that directory.
+
+
Optional variable. No default value.
+
+
+
+
+
+
+
+
+
+
+
Propchange: db/derby/code/trunk/BUILDING.html
------------------------------------------------------------------------------
svn:eol-style = native
Modified: db/derby/code/trunk/java/build/org/apache/derbyPreBuild/PropertySetter.java
URL: http://svn.apache.org/viewvc/db/derby/code/trunk/java/build/org/apache/derbyPreBuild/PropertySetter.java?rev=731605&r1=731604&r2=731605&view=diff
==============================================================================
--- db/derby/code/trunk/java/build/org/apache/derbyPreBuild/PropertySetter.java (original)
+++ db/derby/code/trunk/java/build/org/apache/derbyPreBuild/PropertySetter.java Mon Jan 5 08:09:30 2009
@@ -720,7 +720,7 @@
appendProperty( buffer, OPERATING_SYSTEM );
appendProperty( buffer, J14LIB );
appendProperty( buffer, J15LIB );
- buffer.append( "\nPlease consult BUILDING.txt for instructions on how to set the jdk-library and compiler-classpath properties." );
+ buffer.append( "\nPlease consult BUILDING.html for instructions on how to set the compiler-classpath properties." );
return new BuildException( buffer.toString() );
}
Modified: db/derby/code/trunk/java/testing/README.htm
URL: http://svn.apache.org/viewvc/db/derby/code/trunk/java/testing/README.htm?rev=731605&r1=731604&r2=731605&view=diff
==============================================================================
--- db/derby/code/trunk/java/testing/README.htm (original)
+++ db/derby/code/trunk/java/testing/README.htm Mon Jan 5 08:09:30 2009
@@ -167,7 +167,7 @@
In the following the top directory under which the subversion tree
is placed is referred to as ${derby.source} - see also the derby
BUILDING.txt.
The version of the classes and supporting files of the
derbyTesting package have to match the version of the classes of the
derby package. Thus you either need to build all jars yourself, or
@@ -802,7 +802,7 @@
follow all the steps in the derby BUILDING.txt.
+ href="http://svn.apache.org/repos/asf/db/derby/code/trunk/BUILDING.html">BUILDING.html.
-Before running these tests, you must first build the optional jkd16
-support as described in trunk/BUILDING.txt.
-
-
-
Verifying the JDBC4 feature set is a little tiresome right now. You must
run the following commands in a shell window whose JAVA_HOME points at
your jdk1.6 installation. After each suite run, check the test results.
Modified: db/derby/code/trunk/java/testing/org/apache/derbyTesting/functionTests/tests/junitTests/compatibility/testScript.xml
URL: http://svn.apache.org/viewvc/db/derby/code/trunk/java/testing/org/apache/derbyTesting/functionTests/tests/junitTests/compatibility/testScript.xml?rev=731605&r1=731604&r2=731605&view=diff
==============================================================================
--- db/derby/code/trunk/java/testing/org/apache/derbyTesting/functionTests/tests/junitTests/compatibility/testScript.xml (original)
+++ db/derby/code/trunk/java/testing/org/apache/derbyTesting/functionTests/tests/junitTests/compatibility/testScript.xml Mon Jan 5 08:09:30 2009
@@ -34,8 +34,8 @@
This script assumes that you have set the following variables
in the ant.properties file in your user home directory:
- j13lib Set as you would to compile Derby (see trunk/BUILDING.txt).
- j14lib Set as you would to compile Derby (see trunk/BUILDING.txt).
+ j13lib The library directory of your 1.3 JRE
+ j14lib The library directory of your 1.4 JRE
jdk15 The JAVA_HOME of your 1.5 vm.
jdk16 The JAVA_HOME of your 1.6 vm.
Modified: db/derby/code/trunk/tools/release/build.xml
URL: http://svn.apache.org/viewvc/db/derby/code/trunk/tools/release/build.xml?rev=731605&r1=731604&r2=731605&view=diff
==============================================================================
--- db/derby/code/trunk/tools/release/build.xml (original)
+++ db/derby/code/trunk/tools/release/build.xml Mon Jan 5 08:09:30 2009
@@ -38,7 +38,7 @@
-
+