Big Bump plan

[cdietrich]

• bump versions, create r2026-03 tp, finalize 2.42 ref project and prep 2.43 ref project from Prepare Xtext/Xtend 2.43 release notes + adapt documentation #3620
• remove tps older than 2025-12
• bump to java 21 in all config files / tycho update / adapt ref projects to new situation
• introduce 25 constant / remove 17 constant from wizard + ref projects
• adapt minimum deps in boms and manifest to the one of eclipse 202512 (there is somewhere a java util for that @LorenzoBettini wrote)
• update to Tycho 5.0.2 or newer
• update to Guice 7.0 (we already are, at least in bom)
• junit 6 (drop 5 support) 3660
• reference project wizard integ tests
• oomph
• clean no longer needed java version or bundle version switches
• set emf version to the one of 2025-12, same for mwe
• also move mwe to 21 and tycho5

[cdietrich]

@szarnekow please add/edit from your notes

[cdietrich]

#3638

[cdietrich]

have pushed a first big bunch of changes....

[trancexpress]

@cdietrich do you plan moving tests to JUnit 5/6? If so, is there a ticket? I have some time, I can try doing this.

[cdietrich]

I don’t have any plans in that regard. Also no capacity

[trancexpress]

Regardless of capacity, is it desired to move the tests to JUnit 5?

[cdietrich]

I don’t think there is much benefit and if I got Andrey right in junit 7 everything will be different again

[LorenzoBettini]

@cdietrich do you plan moving tests to JUnit 5/6? If so, is there a ticket? I have some time, I can try doing this.

IMHO, I'd stay with JUnit 4 as much as possible ;)
Things might be different when they remove Jupiter vintage, but, IIRC, at least we don't have mixture of JUnit 4 and JUnit 5 tests in the same project.

In my experience, JUnit 5 only gave me trouble and headaches, especially strange runtime errors, due to its "modular" approach that only introduces complexity.