From 5977636fd9a0660e0f9c94e549137061c381bcb7 Mon Sep 17 00:00:00 2001 From: Suby S Surendran Date: Mon, 27 May 2024 15:38:11 +0530 Subject: [PATCH] Migration Guide Eclipse 4.32 (#2042) --- .../porting/4.32/faq.html | 20 ++++++++++ .../porting/4.32/incompatibilities.html | 19 +++++++++ .../porting/4.32/recommended.html | 23 +++++++++++ .../porting/eclipse_4_32_porting_guide.html | 39 +++++++++++++++++++ .../topics_Porting.xml | 20 ++++++---- .../porting/4.32/faq.html | 13 +++++++ .../porting/4.32/incompatibilities.html | 24 ++++++++++++ .../porting/4.32/recommended.html | 25 ++++++++++++ .../porting/eclipse_4_32_porting_guide.html | 35 +++++++++++++++++ .../topics_Porting.xml | 20 ++++++---- 10 files changed, 224 insertions(+), 14 deletions(-) create mode 100644 eclipse.platform.common/bundles/org.eclipse.jdt.doc.isv/porting/4.32/faq.html create mode 100644 eclipse.platform.common/bundles/org.eclipse.jdt.doc.isv/porting/4.32/incompatibilities.html create mode 100644 eclipse.platform.common/bundles/org.eclipse.jdt.doc.isv/porting/4.32/recommended.html create mode 100644 eclipse.platform.common/bundles/org.eclipse.jdt.doc.isv/porting/eclipse_4_32_porting_guide.html create mode 100644 eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/porting/4.32/faq.html create mode 100644 eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/porting/4.32/incompatibilities.html create mode 100644 eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/porting/4.32/recommended.html create mode 100644 eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/porting/eclipse_4_32_porting_guide.html diff --git a/eclipse.platform.common/bundles/org.eclipse.jdt.doc.isv/porting/4.32/faq.html b/eclipse.platform.common/bundles/org.eclipse.jdt.doc.isv/porting/4.32/faq.html new file mode 100644 index 00000000000..67a6249a6b3 --- /dev/null +++ b/eclipse.platform.common/bundles/org.eclipse.jdt.doc.isv/porting/4.32/faq.html @@ -0,0 +1,20 @@ + + + + + + + +Eclipse JDT 4.32 Plug-in Migration FAQ + + + + +

Eclipse JDT 4.32 Plug-in Migration FAQ

+ +
    +
  1. None
    2. +
+ + + \ No newline at end of file diff --git a/eclipse.platform.common/bundles/org.eclipse.jdt.doc.isv/porting/4.32/incompatibilities.html b/eclipse.platform.common/bundles/org.eclipse.jdt.doc.isv/porting/4.32/incompatibilities.html new file mode 100644 index 00000000000..8b51559d988 --- /dev/null +++ b/eclipse.platform.common/bundles/org.eclipse.jdt.doc.isv/porting/4.32/incompatibilities.html @@ -0,0 +1,19 @@ + + + + + + + +Incompatibilities between Eclipse 4.31 and 4.32 + + +

Incompatibilities between Eclipse 4.31 and 4.32

+ +

+ So far Eclipse did not change incompatibly between 4.31 and 4.32 in ways that affect + plug-ins. Plug-ins that ran on 4.31 should run on 4.32 without any problems. +

+ + + \ No newline at end of file diff --git a/eclipse.platform.common/bundles/org.eclipse.jdt.doc.isv/porting/4.32/recommended.html b/eclipse.platform.common/bundles/org.eclipse.jdt.doc.isv/porting/4.32/recommended.html new file mode 100644 index 00000000000..67f026eb0c1 --- /dev/null +++ b/eclipse.platform.common/bundles/org.eclipse.jdt.doc.isv/porting/4.32/recommended.html @@ -0,0 +1,23 @@ + + + + + + + +Adopting JDT 4.32 mechanisms and APIs + + + + +

Adopting JDT 4.32 mechanisms and APIs

+

+ This section describes changes that are required if you are trying to change + your 4.31 plug-in to adopt the 4.32 mechanisms and APIs. +

+ +
    +
  1. None
    2. +
+ + \ No newline at end of file diff --git a/eclipse.platform.common/bundles/org.eclipse.jdt.doc.isv/porting/eclipse_4_32_porting_guide.html b/eclipse.platform.common/bundles/org.eclipse.jdt.doc.isv/porting/eclipse_4_32_porting_guide.html new file mode 100644 index 00000000000..0e279d1cf27 --- /dev/null +++ b/eclipse.platform.common/bundles/org.eclipse.jdt.doc.isv/porting/eclipse_4_32_porting_guide.html @@ -0,0 +1,39 @@ + + + + + + + + + + +Eclipse JDT 4.32 Plug-in Migration Guide + + + + +

Eclipse JDT 4.32 Plug-in Migration Guide

+

This guide covers migrating Eclipse JDT 4.31 plug-ins to Eclipse JDT 4.32.

+

One of the goals of Eclipse 4.32 was to move Eclipse forward while remaining compatible + with previous versions to the greatest extent possible. That is, plug-ins written + against the Eclipse 4.31 APIs should continue to work in 4.32 in spite of the + API changes.

+

The key kinds of compatibility are API contract compatibility and binary compatibility. + API contract compatibility means that valid use of 4.31 APIs remains valid for + 4.32, 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 ("binary") code to no longer link and run with the + new 4.32 libraries.

+

While every effort was made to avoid breakage, there are a few areas of incompatibility or new + APIs that should be adopted by clients. + This document describes those areas and provides instructions for migrating 4.31 plug-ins to + 4.32.

+ + + + \ No newline at end of file diff --git a/eclipse.platform.common/bundles/org.eclipse.jdt.doc.isv/topics_Porting.xml b/eclipse.platform.common/bundles/org.eclipse.jdt.doc.isv/topics_Porting.xml index 74b84f215c2..437bbeaf4c0 100644 --- a/eclipse.platform.common/bundles/org.eclipse.jdt.doc.isv/topics_Porting.xml +++ b/eclipse.platform.common/bundles/org.eclipse.jdt.doc.isv/topics_Porting.xml @@ -4,6 +4,12 @@ + + + + + + @@ -22,13 +28,13 @@ - - - - - - - + + + + + + + diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/porting/4.32/faq.html b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/porting/4.32/faq.html new file mode 100644 index 00000000000..622b0de5a45 --- /dev/null +++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/porting/4.32/faq.html @@ -0,0 +1,13 @@ + + + + + + + +Eclipse 4.32 Plug-in Migration FAQ + + +

Eclipse 4.32 Plug-in Migration FAQ

+ + \ No newline at end of file diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/porting/4.32/incompatibilities.html b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/porting/4.32/incompatibilities.html new file mode 100644 index 00000000000..69c1cc955b9 --- /dev/null +++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/porting/4.32/incompatibilities.html @@ -0,0 +1,24 @@ + + + + + + + +Incompatibilities between Eclipse 4.31 and 4.32 + + +

Incompatibilities between Eclipse 4.31 and 4.32

+ +

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

+

+See also the list of deprecated API removals for this release. +

+ + + \ No newline at end of file diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/porting/4.32/recommended.html b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/porting/4.32/recommended.html new file mode 100644 index 00000000000..5dbaaf8fbc9 --- /dev/null +++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/porting/4.32/recommended.html @@ -0,0 +1,25 @@ + + + + + + + + + Adopting 4.32 mechanisms and APIs + + + +

Adopting 4.32 mechanisms and APIs

+ +

This section describes changes that are required if you are + trying to change your 4.31 plug-in to adopt the 4.32 mechanisms and + APIs.

+ + + + + + \ No newline at end of file diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/porting/eclipse_4_32_porting_guide.html b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/porting/eclipse_4_32_porting_guide.html new file mode 100644 index 00000000000..1213bed13a3 --- /dev/null +++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/porting/eclipse_4_32_porting_guide.html @@ -0,0 +1,35 @@ + + + + + + + +Eclipse 4.32 Plug-in Migration Guide + + + + +

Eclipse 4.32 Plug-in Migration Guide

+

This guide covers migrating Eclipse 4.31 plug-ins to Eclipse 4.32.

+

One of the goals of Eclipse 4.32 was to move Eclipse forward while remaining compatible + with previous versions to the greatest extent possible. That is, plug-ins written + against the Eclipse 4.31 APIs should continue to work in 4.32 in spite of any API changes.

+

The key kinds of compatibility are API contract compatibility and binary compatibility. + API contract compatibility means that valid use of 4.31 APIs remains valid for + 4.32, 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 ("binary") code to no longer link and run with the + new 4.32 libraries.

+

While every effort was made to avoid breakage, there are a few areas of incompatibility or new + APIs that should be adopted by clients. + This document describes those areas and provides instructions for migrating 4.31 plug-ins to + 4.32.

+ + + + \ No newline at end of file diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/topics_Porting.xml b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/topics_Porting.xml index cf0b56f6302..b8b8357b9e3 100644 --- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/topics_Porting.xml +++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/topics_Porting.xml @@ -5,6 +5,12 @@ + + + + + + @@ -29,13 +35,13 @@ - - - - - - - + + + + + + +