lt;plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-compiler-plugin</artifactId> <configuration> <verbose>true</verbose> <fork>true</fork> <executable><!-- path-to-javac --></executable> <compilerVersion>1.3</compilerVersion> </configuration> </plugin>

The stack is compiled with JDK 1.4.1. The packages uk.co.westhawk.nothread.oscar and uk.co.westhawk.nothread.trap have to be compliant with JDK 1.2.X, since that is what Oracle™ 9i supports. However, this can be done by setting the javac target option to 1.2.

Version 1.0 requires JDK 1.4 or higher. The version in CVS HEAD and future releases will require JDK 1.5 or higher. However, some users have contributed patches to make later versions compatible with JDK 1.4. Please check the contributions/ directory for any such patches. Note that any code in this directory is untested and unsupported, so please use at your own risk and do not file bugs based on that code.

The recommended JDK is version 1.1.8. However, on Windows, version 1.1.7 should work fine. On Solaris using 1.1.7, dialog boxes come up larger than full screen, along with several other annoying user-interface quirks.

Reducing the timeout interval often reduces execution time significantly. Not performing memory leak testing also reduces execution time. Not performing null value tests also helps reduce execution time.

PD4ML is intended to be used with JDK1.4 and above, although it works with minor restrictions under JDK1.3.1 as well.

The current version is designed for Sun JDK 1.3, but will also run on JDK 1.4, 1.5 and 1.6. Both Sun and IBM JDKs are supported. LICENSING INFORMATION

JDK 1.4 is the minimum version required. MapViewer will not work with JDK 1.3 or any earlier version. Also note that if you are using a standalone OC4J instance, you must start it using the Java executable that is under your JDK installation's top bin directory. The java executable under the jre/bin directory will NOT work with OC4J.

We recommend Sun's SDK for Java 1.4 or 1.3. Xindice will not work with the SDK 1.2 or earlier. When using 1.3, be aware that there are known issues with Sun's SDK for Java 1.3.1 on several Linux distributions, but 1.3.0 or 1.4.2 should work without any problems.

I am using Process.waitFor() to force my application written for the Java platform to wait until the native process has finished...

After the installation start JCreator, open the Options dialog box from the Configure menu. Choose the tree item 'JDK Profiles' and click on the Edit button. The Profile Settings dialog will now popup. Select the documentation tab and add the root folder (C:\j2sdk1.4.2\doc) of the java documentation directory to the list. Close the dialogs. The error message means that java.exe cannot find the class file. Make sure your project is compiled without any errors.

For some time, I stuck with the 1.3 JDK, refusing to use even 1.4-specific features. But I finally standardized on Java 1.4, and then on 1.5, for the following reasons: There are various features in 1.5 (generics, the for each construct, enums, etc.), that I want to be able to use or experiment with. The regular expression classes that come with 1.

Yes, use the script "replace JDK compiler" in Tools/Configuration and select your other compiler. You may also need to change your options for the compiler in the JDK/Edit Options... dialog. To enter options for your other compiler, just type them in next to the compiler.

XStream has two modes of operation: Pure Java and Enhanced. In pure Java mode, XStream behaves in the same way across different JVMs, however it's features are limited to what reflection allows, meaning it cannot serialize certain classes or fields. In enhanced mode, XStream does not have these limitations, however this mode of operation is not available to all JVMs.

Two problems with handling Decimal conversion on JDK 5.0 (DERBY-74 and DERBY-83) were fixed in Derby 10.1. JDK 5.0 is also known as JDK 1.5.

Any one of them should work fine. We've tested development of Waba programs using Sun's JDK 1.02, JDK 1.1 and JDK 1.2 and Microsoft's SDK for Java. There is code in the Waba bridge classes to ensure you can develop under any of the various versions.

The IDE does currently not work with JDK 1.4.x versions, it instead expects 1.3.x JDKs. The individual tools like Shell, BugZ and converter may also work with JDK 1.4.x, but this has not intensively be tested.

Author: John Zukowski (http://www.jguru.com/guru/viewbio.jsp?EID=7) You can find this question answered in the Microsoft Knowledge Base at http://support.microsoft.com/support/kb/articles/q214/8/28.asp. Hint, it isn't JDK 1.2.

The openCRX version determines which openMDX version to use. Depending on your preferred JDK version you select matching distributions of openCRX and openMDX for the same JDK.

CA supports JDK 1.3.1 and higher. It understands JDK 1.5 syntax such as new keywords and language changes.

Note: for Windows or Linux user, jdk is already included in our download package, you don't have to bother to install it manually again.

We're open-sourcing these components from an early build of JDK 7. JDK 6 is the current shipping production release, and is stable. Hence we're releasing these components from the JDK 7 tree. At this stage, the only significant differences between the JDK 6 and 7 versions of these components are minor bug fixes and enhancements that have already been integrated into the JDK 7 tree. JDK 7 is the next feature release where all the action will be for innovation and new capabilities.

If for any reason it is impossible for you to upgrade your JRE or JDK software to the latest update versions, Sun has produced a tool for updating time zone data in installed JRE or JDK software images. This is called the US DST Time Zone Updater Tool, or TZupdater, it can be downloaded for free, and it can be applied to versions 1.4.x and later of the Java SE platform. NOTE: A version of the TZupdater tool for JDK/JRE version 1.3.

There is a known limitation with the 1.3.1 JDK in relation to it calculating the correct time for entering and exiting DST transitions. This behavior has been present since 1.3.1 FCS. It has been corrected in 1.4 and in later JDK versions when the time zone framework was re-coded. The limitation arises from complexities in determining whether a given timestamp is in standard or daylight time savings rules.

ShapeLogic is compiled with JDK version 1.6. There are parts of it that is using the JSR 223 scripting framework, introduced in 1.6. It might be possible to compiled it with JDK 1.5.

Version 1.0.0 is out, and very stable. Get the production version, and get rid of all your old developer versions!