Follow Techotopia on Twitter

On-line Guides
All Guides
eBook Store
iOS / Android
Linux for Beginners
Office Productivity
Linux Installation
Linux Security
Linux Utilities
Linux Virtualization
Linux Kernel
System/Network Admin
Scripting Languages
Development Tools
Web Development
GUI Toolkits/Desktop
Mail Systems
Eclipse Documentation

How To Guides
General System Admin
Linux Security
Linux Filesystems
Web Servers
Graphics & Desktop
PC Hardware
Problem Solutions
Privacy Policy




EclipseJDT Plug-in Developer Guide
Previous Page Home Next Page

Incompatibilities between Eclipse JDT 3.2 and 3.3

Eclipse changed in incompatible ways between 3.2 and 3.3 in ways that affect plug-ins. The following entries describe the areas that changed and provide instructions for migrating 3.2 plug-ins to 3.3. Note that you only need to look here if you are experiencing problems running your 3.2 plug-in on 3.3.

  1. API contract changes to IClassFile

1. API contract changes to IClassFile

What is affected: Clients that call IClassFile.getType().

Description: In Eclipse 3.2, the method org.eclipse.jdt.core.IClassFile.getType() threw a org.eclipse.jdt.core.JavaModelException. This is no longer the case in Eclipse 3.3! Note that this change has no impact on binary compatibility.

Action required: Clients calling IClassFile.getType() will have to fix possible 'Unreachable catch block for JavaModelException' compiler errors (only if this call is the only one throwing a JavaModelException in the try block). They also should verify for methods calling this API and throwing a JavaModelException that they still need to throw this exception.

  Published under the terms of the Eclipse Public License Version 1.0 ("EPL") Design by Interspire