GEF Classic 3.24 Release for Eclipse 2025-06

[azoitl]

trafficstars

This issue is used to track and coordinate the work for the GEF Classic 3.24.0 release to be contributed to the Eclipse 2025-06 release train. It shall serve as checklist as well as template for the upcoming release.

• [x] Create 3.24 Milestone
• [x] Update version number and target platforms:
  • [x] Update the version number of all features to 3.24.0
  • [x] Bump maintenance version number of all plugins
  • [x] Update the target platform for the API baseline to GEF Classic 3.24.0
  • [x] Update the pom file target platform checking to GEF Classic 3.24.0
  • [x] Update the development target platform to Eclipse 2025-06
• [x] 07.04.2025: Release 3.24.0 M1 for 2025-06 M1
  • [x] create release record
• [x] 28.04.2025: Release 3.24.0 M2 for 2025-06 M2
• [ ] 19.05.2025: Release 3.24.0 M3 for 2025-06 M3
• [ ] 26.05.2025: Release 3.24.0 RC1 for 2025-06 RC1
• [ ] 02.06.2025: Release 3.24.0 for 2025-06 RC2
  • [ ] create R3_24_maintenance branch
• [ ] 11.06.2025: 2025-06 Release
  • [ ] tag release commit and mark it as release in Github, create release notes

[azoitl]

@ptziegler I tried to do the milestone release but somehow our maven build fails. I could trace the problem back till #705 but I'm not really sure what the problem is as we get strange exception from junit. I tried to upgrade to Tycho 4.0.12 but then I get complaints about Java 17. Do you have any idea what is wrong here?

[merks]

I think you must update tycho because older versions don’t work with latest junit.

I had to tweak a bunch of things to get datatools working

https://github.com/eclipse-datatools/datatools/commit/daaa60f9523d48cc6a65d3b14c97cbba2a06ad91

This in the target configuration is likely key

<executionEnvironment>JavaSE-21</executionEnvironment>

[ptziegler]

Hm... The main problem is that the Draw2D tests are no longer executed, which then leads to an error as no results can be recorded.

It works with Tycho 4.0.12 and Java 21 as @merks said, so my guess is that one of the M1's is mixing up the JUnit 5 plugin that is used for the tests.

There is an incompatibility between Tycho 4.0.10 and JUnit 5.12 which is likely the root cause. So as a short-term solution, I think we really can't build and test with Java 17 anymore...

[azoitl]

Based on @merks feedback I upgraded to Tycho 4.0.12. Locally the build runs now. lets see what PR #716 does in its actions.

[azoitl]

Created release in PMI: https://projects.eclipse.org/projects/tools.gef/releases/gef-classic-3.24.0

[azoitl]

GEF Classic 2024-06 M1 available at:

• Update site: https://download.eclipse.org/tools/gef/classic/milestone/S202504080630
• Simrel contribution: https://github.com/eclipse-simrel/simrel.build/commit/7f760d8c1f13d3fb24ac67f883af083a11a71ab0

[ptziegler]

@azoitl Given the infrastructure issues, I don't think it makes sense to contribute a M2 today if there isn't even a Platform build available. Not that we could, given that the Jenkins is down...

[azoitl]

@azoitl Given the infrastructure issues, I don't think it makes sense to contribute a M2 today if there isn't even a Platform build available. Not that we could, given that the Jenkins is down...

Yes I totally agree. Also there just was an e-mail on the simrel mailing list to anyhow postpone M2 for full week.

[ptziegler]

https://www.eclipse.org/lists/eclipse.org-committers/msg01496.html

To avoid prolonging the outage any further, we have two options:

• We can provision a Jenkins instance with the last known version of the Jenkins data. This data is the last snapshot prior to migration to the storage cluster, and, depending on when your instance was migrated, may be weeks, or up to several months old.
• We can provision a new, bare Jenkins instance for your project. If your build is defined in pipelines alongside your code, recovery may be more straightforward.

I think the GitHub integration for the build warnings will break when restoring the backup, but going this way is likely still the most efficient route.

When you’re ready to proceed, please file an issue on HelpDesk[2] with Project Lead +1 and the team will assist as soon as possible.

That's probably an issue we have to address eventually... I don't think Matthias (or any of the Itemis developers) has even rejoined the eclipse-gef organization...

@azoitl wdyt?

[azoitl]

@ptziegler I also think that restoring from backup is better then starting from a plain jenkins. As you said the thing we loose is your warning checks. I hope that this is not to hard to restore. The only other changes for Jenkins I have in mind are things that @merks did for GEF 5 builds.

And I agree I'm not sure if we will get a +1 from Matthias. But we can try.

[merks]

The backup from November 22, 2024 would include all I did I think.

[azoitl]

Created https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/6005 and also pinged Matthias.

[ptziegler]

As you said the thing we loose is your warning checks.

I think we might not. The required plugins were added on November 19th, so three days before the backup: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/5293

🎉

[merks]

I think the leadership needs to evolve to reflect those who are de facto leading today. I.e., you two.

[ptziegler]

The Jenkins is up again and I took the liberty of contributing the M2: https://download.eclipse.org/tools/gef/classic/milestone/S202505071657 https://github.com/eclipse-simrel/simrel.build/commit/b59cf226263dffdf53a825983cdb047ef55550e9

[azoitl]

The Jenkins is up again and I took the liberty of contributing the M2: https://download.eclipse.org/tools/gef/classic/milestone/S202505071657 eclipse-simrel/simrel.build@b59cf22

Thanks @ptziegler!

[ptziegler]

I think we were only waiting for the infinite loop glitch, so I've already went ahead and contributed the M3: https://github.com/eclipse-simrel/simrel.build/commit/c107159eb4f3037f1067b3d178b80835a49081d3 https://download.eclipse.org/tools/gef/classic/milestone/S202505201944

[azoitl]

GEF Classic 2024-06 R1 is available at:

• Update site: https://download.eclipse.org/tools/gef/classic/milestone/S202505280821
• Simrel contribution: https://github.com/eclipse-simrel/simrel.build/commit/fe80e7d2e9d5c35c9733734aa9ff95379146354b

[azoitl]

As we had no changes since last week I would turn our current RC1 into the release. Are there any objections?

[ptziegler]

Sounds good to me

[azoitl]

GEF Classic Release 3.24 is done:

• Update Site: https://download.eclipse.org/tools/gef/classic/release/3.24.0/index.html
• Simrel contribution: https://github.com/eclipse-simrel/simrel.build/commit/0460adafc55986300742aedf41bbf22d9ef95b24
• Github release: https://github.com/eclipse-gef/gef-classic/releases/tag/R_3_24

Many thanks to all contributors!!!