1+ <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
2+ < html lang ="en ">
3+ < head >
4+ < meta name ="copyright " content ="Copyright (c) IBM Corporation and others 2025. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page. " >
5+ < meta http-equiv ="Content-Type " content ="text/html; charset=ISO-8859-1 ">
6+ < meta http-equiv ="Content-Style-Type " content ="text/css ">
7+ < link rel ="STYLESHEET " href ="../book.css " charset ="ISO-8859-1 " type ="text/css ">
8+ < title > Eclipse 2025-12 (4.38) Plug-in Migration Guide</ title >
9+ </ head >
10+
11+ < body >
12+
13+ < h1 > Eclipse 2025-12 (4.38) Plug-in Migration Guide</ h1 >
14+ < p > This guide covers migrating Eclipse 4.37 plug-ins to Eclipse 4.38.</ p >
15+ < p > One of the goals of Eclipse 4.38 was to move Eclipse forward while remaining compatible
16+ with previous versions to the greatest extent possible. That is, plug-ins written
17+ against the Eclipse 4.37 APIs should continue to work in 4.38 in spite of any API changes.</ p >
18+ < p > The key kinds of compatibility are API contract compatibility and binary compatibility.
19+ API contract compatibility means that valid use of 4.37 APIs remains valid for
20+ 4.38, so there is no need to revisit working code. Binary compatibility means
21+ that the API method signatures, etc. did not change in ways that would cause
22+ existing compiled ("binary") code to no longer link and run with the
23+ new 4.38 libraries.</ p >
24+ < p > While every effort was made to avoid breakage, there are a few areas of incompatibility or new
25+ APIs that should be adopted by clients.
26+ These documents describe those areas and provide instructions for migrating 4.37 plug-ins to
27+ 4.38.</ p >
28+ < ul >
29+ < li > < a href ="https://help.eclipse.org/2025-12/topic/org.eclipse.platform.doc.isv/porting/eclipse_4_38_porting_guide.html?cp=2_3_1_0 ">
30+ Eclipse Platform 2025-12 (4.38) Plug-in Migration Guide</ a > </ li >
31+ < li > < a href ="https://help.eclipse.org/2025-12/topic/org.eclipse.platform.doc.isv/porting/removals.html?cp=2_3_0 ">
32+ Deprecated API removals in Eclipse Platform</ a > </ li >
33+ < li > < a href ="https://help.eclipse.org/2025-06/topic/org.eclipse.jdt.doc.isv/porting/eclipse_4_38_porting_guide.html?cp=3_2_0_0 ">
34+ Eclipse JDT 2025-12 (4.38) Plug-in Migration Guide</ a > </ li >
35+ </ ul >
36+
37+ </ body >
38+ </ html >
0 commit comments