System Requirements

WindowBuilder/SWT Designer/Swing Designer Requirements

  • Windows 2003/XP/Vista or Linux+GTK2

  • OSX (requires Eclipse 3.3 & JDK 1.5 Release 5 Developer Preview 2)

  • Any Eclipse 2.1, 3.0, 3.1, 3.2, 3.3 or 3.4 based IDE

    • Eclipse SDK 2.1.x, 3.0.x, 3.1.x, 3.2.x, 3.3.x or 3.4 (JDK 1.4 or higher)

    • Rational Application Developer 7.0.x

    • Rational Application Developer 6.0.x

    • WebSphere Studio Application Developer (WSAD) 5.1.x

    • WebSphere Studio Site Developer (WSSD) 5.1.x

    • WebSphere Studio Enterprise Developer (WSED) 5.1.x

    • Etc.

GWT Designer Requirements

  • Windows 2003/XP/Vista or Linux+GTK2

  • Mac OSX 10.5 (see OSX Installation instructions)

  • GWT 1.2.22 or higher from http://code.google.com/webtoolkit/download.html

  • GWT 1.4.60 requires GWT Designer 3.0.0 or WindowBuilder 6.5.0 or higher

  • Any Eclipse 3.2, 3.3 or 3.4 based IDE

    • Eclipse SDK 3.2.x, 3.3.x or 3.4

    • Rational Application Developer 7.0.x

    • Etc.


Note that for new Eclipse development streams, we only support releases and stable builds. We do not support nightly or integration builds, and we do not support any unofficial or experimental patches. If you load any patches, you do so at your own risk.


Manually installing features and plug-ins on a FAT file system (Windows only)

Eclipse 3.x and other IDEs based upon Eclipse 3.x may not immediately recognize new tools if they are not installed using the Eclipse Install and Update Manager. This occurs because Eclipse 3.x caches plug-in information for a faster startup at the cost of not recognizing changes to the installed plugins. To workaround this problem, include the "-clean" option on the command line used to startup Eclipse. The "-clean" option causes Eclipse to reparse and recache the plug-in information, picking up any newly installed or revised features. Once the plug-in information has been recached and Designer appears as expected, you can remove the "-clean" option.

Alternatively, you can use the technique described in the Eclipse 3.0 readme file:

When features and plug-ins are manually installed on top of an Eclipse-based product install located on a FAT file system that has already been run at least once, the product must be explicitly restarted with the system property osgi.checkConfiguration set to true. This property can be set in the eclipse/configuration/config.ini file, or passed to the eclipse command line via the -vmargs option. For example, restart with the following command: eclipse.exe -vmargs -Dosgi.checkConfiguration=true. Then, open Help > Software Updates > Manage Configuration dialog and toggle on the "Show disabled features" button its toolbar. Select the newly "installed" feature and press on the "Enable feature" action on the right pane (or select the action from the feature's context menu). (bugs 52525, 66120, 67461).