GEF Project Release Notes

Release 3.0
Last revised June 25, 2004

1. Target Platforms
2. Compatibility with Previous Release
3. Known Issues

1. Target Platforms

GEF 3.0 requires the Eclipse 3.0 Rich Client Platform and the optional org.eclipse.ui.views plug-in.  See the Eclipse Platform readme for requirements of the Eclipse platform.

GEF 3.0.x has been tested and validated on the following Java 2 Platform implementations:

Eclipse Reference Platforms
Operating system Processor architecture Window system Java 2 Platform
Microsoft Windows XP Intel x86 Win32 Sun Java 2 SDK, Standard Edition, version 1.4.2_03 for Microsoft Windows
Microsoft Windows XP Intel x86 Win32 IBM 32-bit SDK for Windows, Java 2 Technology Edition, Version 1.4.1
Red Hat Enterprise Linux WS 3 Intel x86 GTK Sun Java 2 SDK, Standard Edition, 1.4.2_03 for Linux x86
Red Hat Enterprise Linux WS 3 Intel x86 GTK IBM 32-bit SDK for Linux on Intel architecture, Java 2 Technology Edition, Version 1.4.1
SuSE Linux 8.2 Intel x86 GTK Sun Java 2 SDK, Standard Edition, 1.4.2_03 for Linux x86
SuSE Linux 8.2 Intel x86 GTK IBM 32-bit SDK for Linux on Intel architecture, Java 2 Technology Edition, Version 1.4.1
Sun Solaris 8 SPARC Motif Sun Java 2 SDK, Standard Edition, 1.4.2_03 for Solaris SPARC
HP HP-UX 11i hp9000
PA-RISC
Motif HP-UX SDK for the Java 2 platform, version 1.4.2.00 for hp9000 PA-RISC
IBM AIX 5L Version 5.2 PowerPC Motif IBM 32-bit SDK for AIX, Java 2 Technology Edition, Version 1.4.1
Apple Mac OS X 10.3 PowerPC Carbon Java 2 Standard Edition 1.4.1 for Mac OS X

2. Compatibility with Previous Release

API Contract Compatibility: GEF 3.0 is upwards contract-compatible with GEF 2.1 except where the Eclipse Platform .  Downward contract compatibility is not supported. There is no guarantee that compliance with 3.0 APIs would ensure compliance with 2.1 APIs. Refer to Evolving Java-based APIs for a discussion of the kinds of API changes that maintain contract compatibility.

Binary (plug-in) Compatibility: GEF 3.0 is upwards binary-compatible with GEF 2.1 except in those areas noted in the Eclipse 3.0 Plug-in Migration Guide. Eclipse 3.0 will include additional runtime compatibility mechanisms to provide effective binary API compatibility. Downward plug-in compatibility is not supported. Plug-ins for Eclipse SDK 3.0 will not be usable in Eclipse SDK 2.0 or 2.1. Refer to Evolving Java-based APIs for a discussion of the kinds of API changes that maintain binary compatibility.

Non-compliant usage of API's: All non-API methods and classes, and everything in a package with "internal" in its name, are considered implementation details which may vary between operating environment and are subject to change without notice. Client plug-ins that directly depend on anything other than what is specified in the API are inherently unsupportable and receive no guarantees about compatibility within a single release or across releases. Refer to How to Use the Eclipse API for information about how to write compliant plug-ins. 

3. Known Issues

Win32 - Printing

Some fonts scale differently on the printer than they do on the screen. This may result in printed text appearing wider than the same text on the screen. This is only a problem with certain vector fonts.

Images with transparency masks may print incorrectly. This is a limitation in SWT, which GEF uses for printing.

Printing is not implemented on some SWT platforms.


Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.

IBM is a trademark of International Business Machines Corporation in the United States, other countries, or both.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.

Other company, product, and service names may be trademarks or service marks of others.

(c) Copyright Eclipse contributors and others 2004