Attachment 60151 Details for Bug 154667 – New proposed 3.3 porting addition

[patch] New proposed 3.3 porting addition

v02-doc-isv.txt (text/plain), 7.09 KB, created by Frederic Fusier

on 2007-03-02 07:04:03 EST

(hide)

Description:

Filename:

MIME Type:

Creator: Frederic Fusier

Created: 2007-03-02 07:04:03 EST

Size: 7.09 KB

patch

obsolete

>### Eclipse Workspace Patch 1.0
>#P org.eclipse.jdt.doc.isv
>Index: porting/3.3/incompatibilities.html
>===================================================================
>RCS file: porting/3.3/incompatibilities.html
>diff -N porting/3.3/incompatibilities.html
>--- /dev/null	1 Jan 1970 00:00:00 -0000
>+++ porting/3.3/incompatibilities.html	1 Jan 1970 00:00:00 -0000
>@@ -0,0 +1,41 @@
>+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
>+<html>
>+
>+<head>
>+
>+<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
>+
>+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
>+<meta http-equiv="Content-Style-Type" content="text/css">
>+<link rel="STYLESHEET" href="../../book.css" charset="ISO-8859-1" type="text/css">
>+<title>Incompatibilities between Eclipse JDT 3.2 and 3.3</title>
>+</head>
>+
>+<body>
>+
>+<h1>Incompatibilities between Eclipse JDT 3.2 and 3.3</h1>
>+
>+<p> 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.</p>
>+<ol>
>+  <li><a href="#IClassFile">API contract changes to IClassFile</a></li>
>+</ol>
>+<hr>
>+
>+
>+<h2>1. <a name="IClassFile"></a>API contract changes to IClassFile</h2>
>+<p><strong>What is affected:</strong> Clients that call <code>IClassFile.getType()</code>.</p>
>+<p><strong>Description:</strong> In Eclipse 3.2, the method <code>org.eclipse.jdt.core.IClassFile.getType()</code> 
>+  threw a <code>org.eclipse.jdt.core.JavaModelException</code>. This is no longer the case in Eclipse 3.3!
>+  <i>Note that this change has no impact on binary compatibility</i>.</p>
>+<p><strong>Action required:</strong> Clients calling <code>IClassFile.getType()</code> 
>+  will have to fix possible <strong>'Unreachable catch block for JavaModelException'</strong> compiler errors
>+  (only if this call is the only one throwing a <code>JavaModelException</code> in the try block).
>+  They also should verify for methods calling this API and throwing a <code>JavaModelException</code>
>+  that they still need to throw this exception.</p>
>+
>+
>+</body>
>+</html>
>Index: porting/3.3/recommended.html
>===================================================================
>RCS file: porting/3.3/recommended.html
>diff -N porting/3.3/recommended.html
>--- /dev/null	1 Jan 1970 00:00:00 -0000
>+++ porting/3.3/recommended.html	1 Jan 1970 00:00:00 -0000
>@@ -0,0 +1,27 @@
>+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
>+<html>
>+
>+<head>
>+
>+<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
>+
>+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
>+<meta http-equiv="Content-Style-Type" content="text/css">
>+<link rel="STYLESHEET" href="../../book.css" charset="ISO-8859-1" type="text/css">
>+<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
>+<title>Changes required when adopting 3.3 mechanisms and APIs</title>
>+</head>
>+
>+<body>
>+
>+<h1>Changes required when adopting 3.3 mechanisms and APIs</h1>
>+<p>This section describes changes that are required if you are trying to change 
>+  your 3.2 plug-in to adopt the 3.3 mechanisms and APIs.</p>
>+  
>+<ol>
>+	<li>None</li>
>+</ol>
>+
>+</body>
>+
>+</html>
>Index: porting/eclipse_3_3_porting_guide.html
>===================================================================
>RCS file: porting/eclipse_3_3_porting_guide.html
>diff -N porting/eclipse_3_3_porting_guide.html
>--- /dev/null	1 Jan 1970 00:00:00 -0000
>+++ porting/eclipse_3_3_porting_guide.html	1 Jan 1970 00:00:00 -0000
>@@ -0,0 +1,40 @@
>+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
>+<html>
>+
>+<head>
>+
>+<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
>+
>+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
>+<meta http-equiv="Content-Style-Type" content="text/css">
>+<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
>+<title>Eclipse JDT 3.3 Plug-in Migration Guide</title>
>+</head>
>+
>+<body>
>+
>+<h1>Eclipse JDT 3.3 Plug-in Migration Guide</h1>
>+<p>This guide covers migrating Eclipse JDT 3.2 (or earlier) plug-ins to Eclipse JDT 3.3.</p>
>+<p>One of the goals of Eclipse 3.3 was to move Eclipse forward while remaining compatible 
>+  with previous versions to the greatest extent possible. That is, plug-ins written 
>+  against the Eclipse 3.2 APIs should continue to work in 3.3 in spite of the 
>+  API changes.</p>
>+<p>The key kinds of compatibility are API contract compatibility and binary compatibility. 
>+  API contract compatibility means that valid use of 3.2 APIs remains valid for 
>+  3.3, so there is no need to revisit working code. Binary compatibility means 
>+  that the API method signatures, etc. did not change in ways that would cause 
>+  existing compiled (&quot;binary&quot;) code to no longer link and run with the 
>+  new 3.3 libraries.</p>
>+<p>While every effort way made to avoid breakage, there are a few areas of incompatibility. 
>+  This document describes the areas where Eclipse changed in incompatible ways 
>+  between 3.2 and 3.3, and provides instructions for migrating 3.2 plug-ins to 
>+  3.3.</p>
>+<ul>
>+  <li><a href="3.3/faq.html">Eclipse JDT 3.3 Plug-in Migration FAQ</a></li>
>+  <li><a href="3.3/incompatibilities.html">Incompatibilities between Eclipse JDT 3.2 
>+    and 3.3</a></li>
>+  <li><a href="3.3/recommended.html">Adopting 3.3 mechanisms and API</a></li>
>+</ul>
>+
>+</body>
>+</html>
>Index: porting/3.3/faq.html
>===================================================================
>RCS file: porting/3.3/faq.html
>diff -N porting/3.3/faq.html
>--- /dev/null	1 Jan 1970 00:00:00 -0000
>+++ porting/3.3/faq.html	1 Jan 1970 00:00:00 -0000
>@@ -0,0 +1,23 @@
>+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
>+<html>
>+
>+<head>
>+
>+<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
>+
>+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
>+<meta http-equiv="Content-Style-Type" content="text/css">
>+<link rel="STYLESHEET" href="../../book.css" charset="ISO-8859-1" type="text/css">
>+<title>Eclipse JDT 3.3 Plug-in Migration FAQ</title>
>+</head>
>+
>+<body>
>+
>+<h1>Eclipse JDT 3.3 Plug-in Migration FAQ</h1>
>+<ol>
>+	<li>None</li>
>+</ol>
>+
>+</body>
>+
>+</html>

Actions: View | Diff

Attachments on bug 154667: 59666 | 59676 | 59998 | 60151