Skip to content

Commit 8e9d5dd

Browse files
subyssurendran666subyssurendran666
committed
Migration guide foe Eclipse 4.38 from 4.37
1 parent 38f7ba7 commit 8e9d5dd

File tree

10 files changed

+201
-0
lines changed

10 files changed

+201
-0
lines changed

‎eclipse.platform.common/bundles/org.eclipse.jdt.doc.isv/porting/4.38/faq.html‎

Lines changed: 19 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,19 @@
1+
<!DOCTYPE HTML>
2+
<html lang="en">
3+
<head>
4+
<meta name="copyright" content="Copyright (c) 2025 IBM Corporation and others. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
5+
<meta charset="utf-8">
6+
<link rel="STYLESHEET" href="../../book.css">
7+
<title>Eclipse JDT 4.38 Plug-in Migration FAQ</title>
8+
</head>
9+
10+
<body>
11+
12+
<h1>Eclipse JDT 4.38 Plug-in Migration FAQ</h1>
13+
14+
<ol>
15+
<li>None</li>
16+
</ol>
17+
18+
</body>
19+
</html>

‎eclipse.platform.common/bundles/org.eclipse.jdt.doc.isv/porting/4.38/incompatibilities.html‎

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,18 @@
1+
<!DOCTYPE HTML>
2+
<html lang="en">
3+
<head>
4+
<meta name="copyright" content="Copyright (c) 2025 IBM Corporation and others. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
5+
<meta charset="UTF-8">
6+
<link rel="STYLESHEET" href="../../book.css">
7+
<title>Incompatibilities between Eclipse 4.37 and 4.38</title>
8+
</head>
9+
<body>
10+
<h1>Incompatibilities Between Eclipse 4.37 and 4.38</h1>
11+
12+
<p>
13+
So far Eclipse did not change incompatibly between 4.37 and 4.38 in ways that affect
14+
plug-ins. Plug-ins that ran on 4.37 should run on 4.38 without any problems.
15+
</p>
16+
17+
</body>
18+
</html>

‎eclipse.platform.common/bundles/org.eclipse.jdt.doc.isv/porting/4.38/recommended.html‎

Lines changed: 22 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,22 @@
1+
<!DOCTYPE HTML>
2+
<html lang="en">
3+
<head>
4+
<meta name="copyright" content="Copyright (c) 2025 IBM Corporation and others. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
5+
<meta charset="utf-8">
6+
<link rel="STYLESHEET" href="../../book.css">
7+
<title>Adopting JDT 4.38 mechanisms and APIs</title>
8+
</head>
9+
10+
<body>
11+
12+
<h1>Adopting JDT 4.38 Mechanisms and APIs</h1>
13+
<p>
14+
This section describes changes that are required if you are trying to change
15+
your 4.37 plug-in to adopt the 4.38 mechanisms and APIs.
16+
</p>
17+
18+
<ol>
19+
<li>None</li>
20+
</ol>
21+
</body>
22+
</html>

‎eclipse.platform.common/bundles/org.eclipse.jdt.doc.isv/porting/eclipse_4_38_porting_guide.html‎

Lines changed: 38 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,38 @@
1+
<!DOCTYPE HTML>
2+
<html lang="en">
3+
4+
<head>
5+
6+
<meta name="copyright" content="Copyright (c) IBM 2025 Corporation and others. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
7+
8+
<meta charset="utf-8">
9+
<link rel="STYLESHEET" href="../book.css">
10+
<title>Eclipse JDT 4.38 Plug-in Migration Guide</title>
11+
</head>
12+
13+
<body>
14+
15+
<h1>Eclipse JDT 4.38 Plug-in Migration Guide</h1>
16+
<p>This guide covers migrating Eclipse JDT 4.37 plug-ins to Eclipse JDT 4.38.</p>
17+
<p>One of the goals of Eclipse 4.38 was to move Eclipse forward while remaining compatible
18+
with previous versions to the greatest extent possible. That is, plug-ins written
19+
against the Eclipse 4.37 APIs should continue to work in 4.38 in spite of the
20+
API changes.</p>
21+
<p>The key kinds of compatibility are API contract compatibility and binary compatibility.
22+
API contract compatibility means that valid use of 4.37 APIs remains valid for
23+
4.38, so there is no need to revisit working code. Binary compatibility means
24+
that the API method signatures, etc. did not change in ways that would cause
25+
existing compiled (&quot;binary&quot;) code to no longer link and run with the
26+
new 4.38 libraries.</p>
27+
<p>While every effort was made to avoid breakage, there are a few areas of incompatibility or new
28+
APIs that should be adopted by clients.
29+
This document describes those areas and provides instructions for migrating 4.37 plug-ins to
30+
4.38.</p>
31+
<ul>
32+
<li><a href="4.38/faq.html">Eclipse JDT 4.38 Plug-in Migration FAQ</a></li>
33+
<li><a href="4.38/incompatibilities.html">Incompatibilities between Eclipse JDT 4.37 and 4.38</a></li>
34+
<li><a href="4.38/recommended.html">Adopting 4.38 mechanisms and API</a></li>
35+
</ul>
36+
37+
</body>
38+
</html>

‎eclipse.platform.common/bundles/org.eclipse.jdt.doc.isv/topics_Porting.xml‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,12 @@
44
<!-- Define topics for the porting guide index -->
55
<!-- ============================================================================= -->
66
<toc label="Migration">
7+
<topic label="Migrating to Eclipse JDT 4.38 from 4.37">
8+
<topic label="Introduction" href="porting/eclipse_4_38_porting_guide.html"/>
9+
<topic label="FAQ" href="porting/4.38/faq.html" />
10+
<topic label="Incompatibilities" href="porting/4.38/incompatibilities.html" />
11+
<topic label="Adopting 4.38 Mechanisms and API" href="porting/4.38/recommended.html" />
12+
</topic>
713
<topic label="Migrating to Eclipse JDT 4.37 from 4.36">
814
<topic label="Introduction" href="porting/eclipse_4_37_porting_guide.html"/>
915
<topic label="FAQ" href="porting/4.37/faq.html" />

‎eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/porting/4.38/faq.html‎

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
<!DOCTYPE HTML>
2+
<html lang="en">
3+
<head>
4+
<meta name="copyright" content="Copyright (c) 2025 IBM Corporation and others. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
5+
<meta charset="utf-8">
6+
<link rel="STYLESHEET" href="../../book.css" type="text/css">
7+
<title>Eclipse 4.38 Plug-in Migration FAQ</title>
8+
</head>
9+
<body>
10+
<h1>Eclipse 4.38 Plug-in Migration FAQ</h1>
11+
</body>
12+
</html>

‎eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/porting/4.38/incompatibilities.html‎

Lines changed: 23 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,23 @@
1+
<!DOCTYPE HTML>
2+
<html lang="en">
3+
<head>
4+
<meta name="copyright" content="Copyright (c) 2025 IBM Corporation and others. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
5+
<meta charset="utf-8">
6+
<link rel="STYLESHEET" href="../../book.css" type="text/css">
7+
<title>Incompatibilities between Eclipse 4.37 and 4.38</title>
8+
</head>
9+
<body>
10+
<h1>Incompatibilities Between Eclipse 4.37 and 4.38</h1>
11+
12+
<p>
13+
Eclipse changed in incompatible ways between 4.37 and 4.38 in ways that affect
14+
plug-ins. The following entries describe the areas that changed and provide
15+
instructions for migrating 4.37 plug-ins to 4.38. Note that you only need to look
16+
here if you are experiencing problems running your 4.37 plug-in on 4.38.
17+
</p>
18+
<p>
19+
See also the list of <a href="../removals.html">deprecated API removals</a> for this release.
20+
</p>
21+
22+
</body>
23+
</html>

‎eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/porting/4.38/recommended.html‎

Lines changed: 23 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,23 @@
1+
<!DOCTYPE HTML>
2+
<html lang="en">
3+
4+
<head>
5+
<meta name="copyright"
6+
content="Copyright (c) 2025 IBM Corporation and others. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
7+
<meta charset="utf-8">
8+
<link rel="STYLESHEET" href="../../book.css" type="text/css">
9+
<title>Adopting 4.38 mechanisms and APIs</title>
10+
</head>
11+
12+
<body>
13+
<h1>Adopting 4.38 Mechanisms and APIs</h1>
14+
15+
<p>This section describes changes that are required if you are
16+
trying to change your 4.37 plug-in to adopt the 4.38 mechanisms and
17+
APIs.</p>
18+
19+
<!-- ##############################################
20+
############################################## -->
21+
22+
</body>
23+
</html>

‎eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/porting/eclipse_4_38_porting_guide.html‎

Lines changed: 34 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,34 @@
1+
<!DOCTYPE HTML>
2+
<html lang="en">
3+
<head>
4+
<meta name="copyright" content="Copyright (c) 2025 IBM Corporation and others. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
5+
<meta charset="utf-8">
6+
<link rel="STYLESHEET" href="../book.css" type="text/css">
7+
<title>Eclipse 4.38 Plug-in Migration Guide</title>
8+
</head>
9+
10+
<body>
11+
12+
<h1>Eclipse 4.38 Plug-in Migration Guide</h1>
13+
<p>This guide covers migrating Eclipse 4.37 plug-ins to Eclipse 4.38.</p>
14+
<p>One of the goals of Eclipse 4.38 was to move Eclipse forward while remaining compatible
15+
with previous versions to the greatest extent possible. That is, plug-ins written
16+
against the Eclipse 4.37 APIs should continue to work in 4.38 in spite of any API changes.</p>
17+
<p>The key kinds of compatibility are API contract compatibility and binary compatibility.
18+
API contract compatibility means that valid use of 4.37 APIs remains valid for
19+
4.38, so there is no need to revisit working code. Binary compatibility means
20+
that the API method signatures, etc. did not change in ways that would cause
21+
existing compiled (&quot;binary&quot;) code to no longer link and run with the
22+
new 4.38 libraries.</p>
23+
<p>While every effort was made to avoid breakage, there are a few areas of incompatibility or new
24+
APIs that should be adopted by clients.
25+
This document describes those areas and provides instructions for migrating 4.37 plug-ins to
26+
4.38.</p>
27+
<ul>
28+
<li><a href="4.38/faq.html">Eclipse 4.38 Plug-in Migration FAQ</a></li>
29+
<li><a href="4.38/incompatibilities.html">Incompatibilities between Eclipse 4.37 and 4.38</a></li>
30+
<li><a href="4.38/recommended.html">Adopting 4.38 mechanisms and API</a></li>
31+
</ul>
32+
33+
</body>
34+
</html>

‎eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/topics_Porting.xml‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -5,6 +5,12 @@
55
<!-- ============================================================================= -->
66
<toc label="Migration">
77
<topic label="Deprecated API removals" href="porting/removals.html"/>
8+
<topic label="Migrating to Eclipse 4.38 from 4.37">
9+
<topic label="Introduction" href="porting/eclipse_4_38_porting_guide.html"/>
10+
<topic label="FAQ" href="porting/4.38/faq.html" />
11+
<topic label="Incompatibilities" href="porting/4.38/incompatibilities.html" />
12+
<topic label="Adopting 4.38 mechanisms and API" href="porting/4.38/recommended.html" />
13+
</topic>
814
<topic label="Migrating to Eclipse 4.37 from 4.36">
915
<topic label="Introduction" href="porting/eclipse_4_37_porting_guide.html"/>
1016
<topic label="FAQ" href="porting/4.37/faq.html" />

0 commit comments

Comments
 (0)