Incompatibilities Between Eclipse 4.24 and 4.25

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

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

1. Several bundles renamed for 3rd party libraries
2. Different Import-Package version for some 3rd party libraries

1. Different Providers for 3rd Party Packages May Result on Unmatched Required-Bundle

What is affected: Clients that use Require-Bundle with a bundle that was replaced in their target platform.

• JUnit 5 bundles now have name of the form junit-* instead of Orbit variants org.junit.*,
• API Guardian bundle is now named org.apiguardian.api instead of Orbit variant org.apiguardian,
• BouncyCastle bundles are now directly named bcprog and bcpg directly instead of Orbit variants org.bouncycastle.*,
• JSP API bundles is now named javax.servlet.jsp-api instead of Orbit variant javax.servlet.jsp

Description:

Upstream bundles as officially provided by the 3rd-party projects are not shipped by default by Platform instead of Orbit's one. In some cases, the bundle has a different Bundle-SymbolicName than the legacy one.

As a result, some Require-Bundle requirements that used to be satisfied using Orbit-provided bundles may now not be satisfied with upstream bundles, preventing proper installation or execution.

Action required:

1. Replace usage of Require-Bundle by Import-Package which will pick the best provider available in target-platfrm, or
2. Adjust Require-Bundle directives in MANIFEST.MF for the affected bundles, replacing with newer variants, or
3. Adjust your target-platform so it includes the legacy Orbit variants for the mentioned bundles

2. Different Providers for 3rd Party Packages May Result on Unmatched Import-Package Requirements

What is affected: Clients that use Import-Package with a version requirement for some 3rd-party packages:

• com.ibm.icu

Description:

Upstream bundles as provided by the 3rd-party projects are not shipped by default by Platform instead of Orbit's one. Orbit usually add a version on package exports; this version does not match what upstream projects define.

As a result, some Import-Package requirements that used to be satisfied using Orbit-provided bundles may now not be satisfied with upstream bundles, preventing proper installation or execution.

Action required:

1. Adjust Import-Pacakge directives in MANIFEST.MF for the affected packages, either by removing the version requirement or by fixing it according to new upstream provider (recommended), or
2. Update your build script and other package definition to force inclusion of legacy Orbit-provided bundles