Sqlch was written using Java 1.3.1 and Java 1.4.2. It should run with Java 1.3.1 and above. Some JDBC Drivers have more restrictive requirements that might require you to use later versions of Java. Sqlch only directly uses the J2SE APIs - no other Sun standard Java APIs are needed.
Sqlch was developed against Ant 1.6.1. It would have been better to use an earlier version (e.g. 1.4.1) to ensure a wider audience but unfortunately version 1.6.1 introduced new features that were just too useful to be ignored. The new features being used are mainly the macrodef and typedef tasks.
If you do not intend to use the Ant integration of Sqlch and want to code directly against the Sqlch API (you crazy fool) you will still need parts of Ant in your CLASSPATH. This is because Sqlch uses the filtering/token replacement functionality that Ant provides. If you are just using the Sqlch API you should still be able to use Ant 1.4.1 since the Ant APIs around the token-replacement code do not appear to have changed significantly (no guarantees!). In the future this dependency should be broken once somebody can be bothered to re-implement the token replacement using reg-exp's (probably).
Sqlch does not come with JDBC drivers. You will need to find one for your database. This is mainly to avoid any legal issues that bundling drivers may introduce. Sqlch has been tested with a few databases and a few versions of the drivers for those databases. See this page for more information. The best thing to do is to try it with your driver and see what happens.
Sqlch uses the JAXP 1.1 API and comes with the xml-apis.jar file from Apache Xerces to provide the necessary interfaces. If you are using an environment where these classes are available in another form, you can lose this JAR.
See the LICENSE.sax and LICENSE.dom files in the root directory of the distribution for legal blurb associated with the JAXP API.
Sqlch was developed using the Xerces parser, however it should (in theory) work with any correctly configured JAXP 1.1-compatible parser. Sqlch also makes use of the org.apache.xml.serialize classes that come with Xerces to generate XML files, so you will usually need to keep the xercesImpl.jar around even if you intend to use an alternative parser.
See the LICENSE.xerces file in the root directory of the distribution for legal blurb associated with the Xerces parser.
Sqlch uses the Common-codec API for Base64 encoding/decoding of binary data. There is a compile-time dependency on this library. However, if you are not using any of the ColumnHelpers that deal with binary data you can exclude the commons-codec-*.jar file at runtime.
See the LICENSE.commons-codec file in the root directory of the distribution for legal blurb associated with the Xerces parser.
Sqlch SourceForge Distribution: 0.1Alpha8 20041026 2208