Migrate framework to Eclipse E4.37 and update Maven build plugins

[bahnwaerter]

The changes migrate the Equinox framework with all its components from Eclipse E4.32 to E4.37. The Java version remains unchanged at version 21. In addition, the Maven build plugins are updated to their latest stable version. Architecture and operating system-specific platform targets are obsolete and are no longer needed, since the specific framework dependencies (Eclipse plugins) are now listed in the feature files of Ultimate. From now on, only the general Ultimate.target needs to be used as the platform target and all required framework dependencies will then be resolved automatically according to the content of the feature files.

[bahnwaerter]

These changes also facilitate the implementation of the desired feature in #749. However, the implementation will be done in a separate pull request.

[bahnwaerter]

The changes have already been tested manually. It is possible to build and run Ultimate based on Eclipse E4.37 under

• Linux (Arch Linux)
• macOS Ventura
• Windows 10

while using Eclipse 2025-09 as IDE.

It is also possible to build Ultimate using Maven on Linux (Arch Linux) where a Maven version greater than 3.9.9 is required for this.

[schuessf]

So, then this looks good to me. The question is, should we merge this before SV-COMP or is this somehow "too risky"?

[bahnwaerter]

[...] The question is, should we merge this before SV-COMP or is this somehow "too risky"?

I would tend to merge these changes after SV-COMP. We also don't have any performance comparison yet. Also, it's unclear whether the Eclipse compiler update will cause further problems (as it was last year the case).

[schuessf]

With this framework migration, the version of org.eclipse.equinox.launcher has also changed, right? If this is the case, several hardcoded version strings (e.g., in Ultimate.py) still have to be adapted.

[bahnwaerter]

With this framework migration, the version of org.eclipse.equinox.launcher has also changed, right? [...]

That's correct, thanks for the hint. I just adjusted the filename of the launcher Jar in the startup scripts.

[schuessf]

I just rebased this MR and started the nightly to check if it succeeds (required 7826bda as a small fix).
Since Eclipse 2025-12 is out now, can you check if we can directly upgrade to this version (not urgent though)?

[schuessf]

Unfortunately, there was still some issue that lead to all tests failing, but I hopefully fixed that in 26d3096.
Also, I just tried updating to 2025-12 (and cleaning up the target file): https://github.com/ultimate-pa/ultimate/tree/wip/fs/update-target
Let's see, if it is working 🙂