You need to install a JDK, for example the Sun JDK version 1.4, 1.5 or 1.6. On the command line, go to the directory h2 and execute the following command:
You need to install a JDK, for example the Sun JDK version 1.4, 1.5 or 1.6. On the command line, go to the directory h2 and execute the following command:
@build_1023_p
@build_1026_p
For Linux and OS X, use <code>./build.sh</code> instead of <code>build</code> .
For Linux and OS X, use <code>./build.sh</code> instead of <code>build</code> .
@build_1024_p
@build_1027_p
You will get a list of targets. If you want to build the jar file, execute (Windows):
You will get a list of targets. If you want to build the jar file, execute (Windows):
@build_1025_h3
@build_1028_h3
Switching the Source Code
Switching the Source Code
@build_1026_p
@build_1029_p
By default the source code uses Java 1.5 features, however Java 1.4 and 1.5 are supported as well. To switch the source code to the install version of Java, run:
By default the source code uses Java 1.5 features, however Java 1.4 and 1.5 are supported as well. To switch the source code to the install version of Java, run:
@build_1027_h2
@build_1030_h2
Build Targets
Build Targets
@build_1028_p
@build_1031_p
The build system can generate smaller jar files as well. The following targets are currently supported:
The build system can generate smaller jar files as well. The following targets are currently supported:
@build_1029_li
@build_1032_li
jarClient: Create the h2client.jar. This only contains the JDBC client.
jarClient: Create the h2client.jar. This only contains the JDBC client.
@build_1030_li
@build_1033_li
jarSmall: Create the file h2small.jar. This only contains the embedded database. Debug information is disabled.
jarSmall: Create the file h2small.jar. This only contains the embedded database. Debug information is disabled.
@build_1031_li
@build_1034_li
jarJaqu: Create the file h2jaqu.jar. This only contains the JaQu (Java Query) implementation. All other jar files do not include JaQu.
jarJaqu: Create the file h2jaqu.jar. This only contains the JaQu (Java Query) implementation. All other jar files do not include JaQu.
@build_1032_li
@build_1035_li
javadocImpl: Create the Javadocs of the implementation.
javadocImpl: Create the Javadocs of the implementation.
@build_1033_p
@build_1036_p
To create the h2client.jar file, go to the directory h2 and execute the following command:
To create the h2client.jar file, go to the directory h2 and execute the following command:
@build_1034_h2
@build_1037_h2
Using Maven 2
Using Maven 2
@build_1035_h3
@build_1038_h3
Using a Central Repository
Using a Central Repository
@build_1036_p
@build_1039_p
You can include the database in your Maven 2 project as a dependency. Example:
You can include the database in your Maven 2 project as a dependency. Example:
@build_1037_p
@build_1040_p
New versions of this database are first uploaded to http://hsql.sourceforge.net/m2-repo/ and then automatically synchronized with the main maven repository; however after a new release it may take a few hours before they are available there.
New versions of this database are first uploaded to http://hsql.sourceforge.net/m2-repo/ and then automatically synchronized with the main maven repository; however after a new release it may take a few hours before they are available there.
@build_1038_h3
@build_1041_h3
Using Snapshot Version
Using Snapshot Version
@build_1039_p
@build_1042_p
To build a 'snapshot' H2 .jar file and upload it the to the local Maven 2 repository, execute the following command:
To build a 'snapshot' H2 .jar file and upload it the to the local Maven 2 repository, execute the following command:
@build_1040_p
@build_1043_p
Afterwards, you can include the database in your Maven 2 project as a dependency:
Afterwards, you can include the database in your Maven 2 project as a dependency:
@build_1041_h2
@build_1044_h2
Translating
Translating
@build_1042_p
@build_1045_p
The translation of this software is split into the following parts:
The translation of this software is split into the following parts:
To translate the H2 Console, start it and select Preferences / Translate. The conversion between UTF-8 and Java encoding (using the \u syntax), as well as the HTML entities (&#..;) is automated by running the tool PropertiesToUTF8. The web site translation is automated as well, using <code>build docs</code> .
To translate the H2 Console, start it and select Preferences / Translate. The conversion between UTF-8 and Java encoding (using the \u syntax), as well as the HTML entities (&#..;) is automated by running the tool PropertiesToUTF8. The web site translation is automated as well, using <code>build docs</code> .
@build_1047_h2
@build_1050_h2
Providing Patches
Providing Patches
@build_1048_p
@build_1051_p
If you like to provide patches, please consider the following guidelines to simplify merging them:
If you like to provide patches, please consider the following guidelines to simplify merging them:
@build_1049_li
@build_1052_li
Only use Java 1.4 features (do not use Java 1.5 or 1.6) (see Environment).
Only use Java 1.4 features (do not use Java 1.5 or 1.6) (see Environment).
@build_1050_li
@build_1053_li
Follow the coding style used in the project, and use Checkstyle (see above) to verify. For example, do not use tabs (use spaces instead). The checkstyle configuration is in <code>src/installer/checkstyle.xml</code> .
Follow the coding style used in the project, and use Checkstyle (see above) to verify. For example, do not use tabs (use spaces instead). The checkstyle configuration is in <code>src/installer/checkstyle.xml</code> .
@build_1051_li
@build_1054_li
Please provide test cases and integrate them into the test suite. For Java level tests, see <code>src/test/org/h2/test/TestAll.java</code> . For SQL level tests, see <code>src/test/org/h2/test/test.in.txt</code> or <code>testSimple.in.txt</code> .
Please provide test cases and integrate them into the test suite. For Java level tests, see <code>src/test/org/h2/test/TestAll.java</code> . For SQL level tests, see <code>src/test/org/h2/test/test.in.txt</code> or <code>testSimple.in.txt</code> .
@build_1052_li
@build_1055_li
The test cases should cover at least 90% of the changed and new code; use a code coverage tool to verify that (see above).
The test cases should cover at least 90% of the changed and new code; use a code coverage tool to verify that (see above). or use the build target 'coverage'.
@build_1053_li
@build_1056_li
Verify that you did not break other features: Run the test cases by executing <code>build test</code> .
Verify that you did not break other features: Run the test cases by executing <code>build test</code> .
@build_1054_li
@build_1057_li
Provide end user documentation if required ( <code>src/docsrc/html/*</code> ).
Provide end user documentation if required ( <code>src/docsrc/html/*</code> ).
@build_1055_li
@build_1058_li
Document grammar changes in <code>src/main/org/h2/res/help.csv</code>
Document grammar changes in <code>src/main/org/h2/res/help.csv</code>
@build_1056_li
@build_1059_li
Provide a change log entry ( <code>src/docsrc/html/changelog.html</code> ).
Provide a change log entry ( <code>src/docsrc/html/changelog.html</code> ).
@build_1057_li
@build_1060_li
Verify the spelling using <code>build spellcheck</code> . If required add the new words to <code>src/tools/org/h2/build/doc/dictionary.txt</code> .
Verify the spelling using <code>build spellcheck</code> . If required add the new words to <code>src/tools/org/h2/build/doc/dictionary.txt</code> .
@build_1058_li
@build_1061_li
Verify the formatting using <code>build docs</code> and <code>build javadoc</code> .
Verify the formatting using <code>build docs</code> and <code>build javadoc</code> .
@build_1059_li
@build_1062_li
Submit patches as .patch files (compressed if big). To create a patch using Eclipse, use Team / Create Patch.
Submit patches as .patch files (compressed if big). To create a patch using Eclipse, use Team / Create Patch.
@build_1063_h2
Code Coverage
@build_1064_p
To generate the code coverage data, execute the following command:
@build_1065_p
The code coverage is run regularly, the last results are available here:
@build_1066_a
Overall Coverage Summary
@build_1067_a
Details (download, 1.3 MB)
@changelog_1000_h1
@changelog_1000_h1
Change Log
Change Log
...
@@ -1142,7 +1166,7 @@ Change Log
...
@@ -1142,7 +1166,7 @@ Change Log
Next Version (unreleased)
Next Version (unreleased)
@changelog_1002_li
@changelog_1002_li
-
A file system implementation can now be registered using FileSystem.register. The database file system is no longer included in the jar file, it moved to the test section.
#You need to install a JDK, for example the Sun JDK version 1.4, 1.5 or 1.6. On the command line, go to the directory h2 and execute the following command:
#You need to install a JDK, for example the Sun JDK version 1.4, 1.5 or 1.6. On the command line, go to the directory h2 and execute the following command:
@build_1023_p
@build_1026_p
#For Linux and OS X, use <code>./build.sh</code> instead of <code>build</code> .
#For Linux and OS X, use <code>./build.sh</code> instead of <code>build</code> .
@build_1024_p
@build_1027_p
#You will get a list of targets. If you want to build the jar file, execute (Windows):
#You will get a list of targets. If you want to build the jar file, execute (Windows):
@build_1025_h3
@build_1028_h3
#Switching the Source Code
#Switching the Source Code
@build_1026_p
@build_1029_p
#By default the source code uses Java 1.5 features, however Java 1.4 and 1.5 are supported as well. To switch the source code to the install version of Java, run:
#By default the source code uses Java 1.5 features, however Java 1.4 and 1.5 are supported as well. To switch the source code to the install version of Java, run:
@build_1027_h2
@build_1030_h2
#Build Targets
#Build Targets
@build_1028_p
@build_1031_p
#The build system can generate smaller jar files as well. The following targets are currently supported:
#The build system can generate smaller jar files as well. The following targets are currently supported:
@build_1029_li
@build_1032_li
#jarClient: Create the h2client.jar. This only contains the JDBC client.
#jarClient: Create the h2client.jar. This only contains the JDBC client.
@build_1030_li
@build_1033_li
#jarSmall: Create the file h2small.jar. This only contains the embedded database. Debug information is disabled.
#jarSmall: Create the file h2small.jar. This only contains the embedded database. Debug information is disabled.
@build_1031_li
@build_1034_li
#jarJaqu: Create the file h2jaqu.jar. This only contains the JaQu (Java Query) implementation. All other jar files do not include JaQu.
#jarJaqu: Create the file h2jaqu.jar. This only contains the JaQu (Java Query) implementation. All other jar files do not include JaQu.
@build_1032_li
@build_1035_li
#javadocImpl: Create the Javadocs of the implementation.
#javadocImpl: Create the Javadocs of the implementation.
@build_1033_p
@build_1036_p
#To create the h2client.jar file, go to the directory h2 and execute the following command:
#To create the h2client.jar file, go to the directory h2 and execute the following command:
@build_1034_h2
@build_1037_h2
Maven 2 の利用
Maven 2 の利用
@build_1035_h3
@build_1038_h3
Centralリポジトリの利用
Centralリポジトリの利用
@build_1036_p
@build_1039_p
依存関係を取ることで、Maven 2プロジェクトでデータベースを組み込むことも可能です。例:
依存関係を取ることで、Maven 2プロジェクトでデータベースを組み込むことも可能です。例:
@build_1037_p
@build_1040_p
#New versions of this database are first uploaded to http://hsql.sourceforge.net/m2-repo/ and then automatically synchronized with the main maven repository; however after a new release it may take a few hours before they are available there.
#New versions of this database are first uploaded to http://hsql.sourceforge.net/m2-repo/ and then automatically synchronized with the main maven repository; however after a new release it may take a few hours before they are available there.
#To translate the H2 Console, start it and select Preferences / Translate. The conversion between UTF-8 and Java encoding (using the \u syntax), as well as the HTML entities (&#..;) is automated by running the tool PropertiesToUTF8. The web site translation is automated as well, using <code>build docs</code> .
#To translate the H2 Console, start it and select Preferences / Translate. The conversion between UTF-8 and Java encoding (using the \u syntax), as well as the HTML entities (&#..;) is automated by running the tool PropertiesToUTF8. The web site translation is automated as well, using <code>build docs</code> .
@build_1047_h2
@build_1050_h2
#Providing Patches
#Providing Patches
@build_1048_p
@build_1051_p
#If you like to provide patches, please consider the following guidelines to simplify merging them:
#If you like to provide patches, please consider the following guidelines to simplify merging them:
@build_1049_li
@build_1052_li
#Only use Java 1.4 features (do not use Java 1.5 or 1.6) (see Environment).
#Only use Java 1.4 features (do not use Java 1.5 or 1.6) (see Environment).
@build_1050_li
@build_1053_li
#Follow the coding style used in the project, and use Checkstyle (see above) to verify. For example, do not use tabs (use spaces instead). The checkstyle configuration is in <code>src/installer/checkstyle.xml</code> .
#Follow the coding style used in the project, and use Checkstyle (see above) to verify. For example, do not use tabs (use spaces instead). The checkstyle configuration is in <code>src/installer/checkstyle.xml</code> .
@build_1051_li
@build_1054_li
#Please provide test cases and integrate them into the test suite. For Java level tests, see <code>src/test/org/h2/test/TestAll.java</code> . For SQL level tests, see <code>src/test/org/h2/test/test.in.txt</code> or <code>testSimple.in.txt</code> .
#Please provide test cases and integrate them into the test suite. For Java level tests, see <code>src/test/org/h2/test/TestAll.java</code> . For SQL level tests, see <code>src/test/org/h2/test/test.in.txt</code> or <code>testSimple.in.txt</code> .
@build_1052_li
@build_1055_li
#The test cases should cover at least 90% of the changed and new code; use a code coverage tool to verify that (see above).
#The test cases should cover at least 90% of the changed and new code; use a code coverage tool to verify that (see above). or use the build target 'coverage'.
@build_1053_li
@build_1056_li
#Verify that you did not break other features: Run the test cases by executing <code>build test</code> .
#Verify that you did not break other features: Run the test cases by executing <code>build test</code> .
@build_1054_li
@build_1057_li
#Provide end user documentation if required ( <code>src/docsrc/html/*</code> ).
#Provide end user documentation if required ( <code>src/docsrc/html/*</code> ).
@build_1055_li
@build_1058_li
#Document grammar changes in <code>src/main/org/h2/res/help.csv</code>
#Document grammar changes in <code>src/main/org/h2/res/help.csv</code>
@build_1056_li
@build_1059_li
#Provide a change log entry ( <code>src/docsrc/html/changelog.html</code> ).
#Provide a change log entry ( <code>src/docsrc/html/changelog.html</code> ).
@build_1057_li
@build_1060_li
#Verify the spelling using <code>build spellcheck</code> . If required add the new words to <code>src/tools/org/h2/build/doc/dictionary.txt</code> .
#Verify the spelling using <code>build spellcheck</code> . If required add the new words to <code>src/tools/org/h2/build/doc/dictionary.txt</code> .
@build_1058_li
@build_1061_li
#Verify the formatting using <code>build docs</code> and <code>build javadoc</code> .
#Verify the formatting using <code>build docs</code> and <code>build javadoc</code> .
@build_1059_li
@build_1062_li
#Submit patches as .patch files (compressed if big). To create a patch using Eclipse, use Team / Create Patch.
#Submit patches as .patch files (compressed if big). To create a patch using Eclipse, use Team / Create Patch.
@build_1063_h2
#Code Coverage
@build_1064_p
#To generate the code coverage data, execute the following command:
@build_1065_p
#The code coverage is run regularly, the last results are available here:
@build_1066_a
#Overall Coverage Summary
@build_1067_a
#Details (download, 1.3 MB)
@changelog_1000_h1
@changelog_1000_h1
変更履歴
変更履歴
...
@@ -1144,7 +1168,7 @@ Centralリポジトリの利用
...
@@ -1144,7 +1168,7 @@ Centralリポジトリの利用
#Next Version (unreleased)
#Next Version (unreleased)
@changelog_1002_li
@changelog_1002_li
#-
#A file system implementation can now be registered using FileSystem.register. The database file system is no longer included in the jar file, it moved to the test section.
build_1022_p=You need to install a JDK, for example the Sun JDK version 1.4, 1.5 or 1.6. On the command line, go to the directory h2 and execute the following command\:
build_1023_p=For Linux and OS X, use <code>./build.sh</code> instead of <code>build</code> .
build_1023_a=Maven 2.0.9
build_1024_p=You will get a list of targets. If you want to build the jar file, execute (Windows)\:
build_1024_h2=Building the Software
build_1025_h3=Switching the Source Code
build_1025_p=You need to install a JDK, for example the Sun JDK version 1.4, 1.5 or 1.6. On the command line, go to the directory h2 and execute the following command\:
build_1026_p=By default the source code uses Java 1.5 features, however Java 1.4 and 1.5 are supported as well. To switch the source code to the install version of Java, run\:
build_1026_p=For Linux and OS X, use <code>./build.sh</code> instead of <code>build</code> .
build_1027_h2=Build Targets
build_1027_p=You will get a list of targets. If you want to build the jar file, execute (Windows)\:
build_1028_p=The build system can generate smaller jar files as well. The following targets are currently supported\:
build_1028_h3=Switching the Source Code
build_1029_li=jarClient\:Create the h2client.jar. This only contains the JDBC client.
build_1029_p=By default the source code uses Java 1.5 features, however Java 1.4 and 1.5 are supported as well. To switch the source code to the install version of Java, run\:
build_1030_li=jarSmall\:Create the file h2small.jar. This only contains the embedded database. Debug information is disabled.
build_1030_h2=Build Targets
build_1031_li=jarJaqu\:Create the file h2jaqu.jar. This only contains the JaQu (Java Query) implementation. All other jar files do not include JaQu.
build_1031_p=The build system can generate smaller jar files as well. The following targets are currently supported\:
build_1032_li=javadocImpl\:Create the Javadocs of the implementation.
build_1032_li=jarClient\:Create the h2client.jar. This only contains the JDBC client.
build_1033_p=To create the h2client.jar file, go to the directory h2 and execute the following command\:
build_1033_li=jarSmall\:Create the file h2small.jar. This only contains the embedded database. Debug information is disabled.
build_1034_h2=Using Maven 2
build_1034_li=jarJaqu\:Create the file h2jaqu.jar. This only contains the JaQu (Java Query) implementation. All other jar files do not include JaQu.
build_1035_h3=Using a Central Repository
build_1035_li=javadocImpl\:Create the Javadocs of the implementation.
build_1036_p=You can include the database in your Maven 2 project as a dependency. Example\:
build_1036_p=To create the h2client.jar file, go to the directory h2 and execute the following command\:
build_1037_p=New versions of this database are first uploaded to http\://hsql.sourceforge.net/m2-repo/ and then automatically synchronized with the main maven repository; however after a new release it may take a few hours before they are available there.
build_1037_h2=Using Maven 2
build_1038_h3=Using Snapshot Version
build_1038_h3=Using a Central Repository
build_1039_p=To build a 'snapshot' H2 .jar file and upload it the to the local Maven 2 repository, execute the following command\:
build_1039_p=You can include the database in your Maven 2 project as a dependency. Example\:
build_1040_p=Afterwards, you can include the database in your Maven 2 project as a dependency\:
build_1040_p=New versions of this database are first uploaded to http\://hsql.sourceforge.net/m2-repo/ and then automatically synchronized with the main maven repository; however after a new release it may take a few hours before they are available there.
build_1041_h2=Translating
build_1041_h3=Using Snapshot Version
build_1042_p=The translation of this software is split into the following parts\:
build_1042_p=To build a 'snapshot' H2 .jar file and upload it the to the local Maven 2 repository, execute the following command\:
build_1045_p=The translation of this software is split into the following parts\:
build_1046_p=To translate the H2 Console, start it and select Preferences / Translate. The conversion between UTF-8 and Java encoding (using the \\u syntax), as well as the HTML entities (&\#..;) is automated by running the tool PropertiesToUTF8. The web site translation is automated as well, using <code>build docs</code> .
build_1049_li=Only use Java 1.4 features (do not use Java 1.5 or 1.6) (see Environment).
build_1049_p=To translate the H2 Console, start it and select Preferences / Translate. The conversion between UTF-8 and Java encoding (using the \\u syntax), as well as the HTML entities (&\#..;) is automated by running the tool PropertiesToUTF8. The web site translation is automated as well, using <code>build docs</code> .
build_1050_li=Follow the coding style used in the project, and use Checkstyle (see above) to verify. For example, do not use tabs (use spaces instead). The checkstyle configuration is in <code>src/installer/checkstyle.xml</code> .
build_1050_h2=Providing Patches
build_1051_li=Please provide test cases and integrate them into the test suite. For Java level tests, see <code>src/test/org/h2/test/TestAll.java</code> . For SQL level tests, see <code>src/test/org/h2/test/test.in.txt</code> or <code>testSimple.in.txt</code> .
build_1051_p=If you like to provide patches, please consider the following guidelines to simplify merging them\:
build_1052_li=The test cases should cover at least 90% of the changed and new code; use a code coverage tool to verify that (see above).
build_1052_li=Only use Java 1.4 features (do not use Java 1.5 or 1.6) (see Environment).
build_1053_li=Verify that you did not break other features\:Run the test cases by executing <code>build test</code> .
build_1053_li=Follow the coding style used in the project, and use Checkstyle (see above) to verify. For example, do not use tabs (use spaces instead). The checkstyle configuration is in <code>src/installer/checkstyle.xml</code> .
build_1054_li=Provide end user documentation if required ( <code>src/docsrc/html/*</code> ).
build_1054_li=Please provide test cases and integrate them into the test suite. For Java level tests, see <code>src/test/org/h2/test/TestAll.java</code> . For SQL level tests, see <code>src/test/org/h2/test/test.in.txt</code> or <code>testSimple.in.txt</code> .
build_1055_li=Document grammar changes in <code>src/main/org/h2/res/help.csv</code>
build_1055_li=The test cases should cover at least 90% of the changed and new code; use a code coverage tool to verify that (see above). or use the build target 'coverage'.
build_1056_li=Provide a change log entry ( <code>src/docsrc/html/changelog.html</code> ).
build_1056_li=Verify that you did not break other features\:Run the test cases by executing <code>build test</code> .
build_1057_li=Verify the spelling using <code>build spellcheck</code> . If required add the new words to <code>src/tools/org/h2/build/doc/dictionary.txt</code> .
build_1057_li=Provide end user documentation if required ( <code>src/docsrc/html/*</code> ).
build_1058_li=Verify the formatting using <code>build docs</code> and <code>build javadoc</code> .
build_1058_li=Document grammar changes in <code>src/main/org/h2/res/help.csv</code>
build_1059_li=Submit patches as .patch files (compressed if big). To create a patch using Eclipse, use Team / Create Patch.
build_1059_li=Provide a change log entry ( <code>src/docsrc/html/changelog.html</code> ).
build_1060_li=Verify the spelling using <code>build spellcheck</code> . If required add the new words to <code>src/tools/org/h2/build/doc/dictionary.txt</code> .
build_1061_li=Verify the formatting using <code>build docs</code> and <code>build javadoc</code> .
build_1062_li=Submit patches as .patch files (compressed if big). To create a patch using Eclipse, use Team / Create Patch.
build_1063_h2=Code Coverage
build_1064_p=To generate the code coverage data, execute the following command\:
build_1065_p=The code coverage is run regularly, the last results are available here\:
build_1066_a=Overall Coverage Summary
build_1067_a=Details (download, 1.3 MB)
changelog_1000_h1=Change Log
changelog_1000_h1=Change Log
changelog_1001_h2=Next Version (unreleased)
changelog_1001_h2=Next Version (unreleased)
changelog_1002_li=-
changelog_1002_li=A file system implementation can now be registered using FileSystem.register. The database file system is no longer included in the jar file, it moved to the test section.
changelog_1003_h2=Version 1.1.111 (2009-04-10)
changelog_1003_h2=Version 1.1.111 (2009-04-10)
changelog_1004_li=In-memory databases can now run inside the Google App Engine.
changelog_1004_li=In-memory databases can now run inside the Google App Engine.
changelog_1005_li=Queries that are ordered by an indexed column returned no rows in certain cases (if all rows were deleted from the table previously, and there is a low number of rows in the table, and when not using other conditions, and when using the default b tree index).
changelog_1005_li=Queries that are ordered by an indexed column returned no rows in certain cases (if all rows were deleted from the table previously, and there is a low number of rows in the table, and when not using other conditions, and when using the default b tree index).
