Apache Batik version for 2025-09

[pcdavid]

The latest version of Apache Batik upstream is 1.19 released last May: https://xmlgraphics.apache.org/batik/

It's also the version available in Orbit. I was planning to upgrade GMF Runtime with that version for the next release for 2025-09, but noticed that the current SimRel staging is still providing Batik 1.18 (https://download.eclipse.org/staging/2025-09/plugins/) so reverted the change for now to avoid duplicates.

I'm not familiar with how the platform releng works, but https://github.com/eclipse-platform/eclipse.platform.releng.aggregator/blob/master/eclipse.platform.releng.prereqs.sdk/eclipse-sdk-prereqs.target#L11 seems to indicate that platform should depend on version 1.19, so I'm a little confused.

Am I looking at the wrong place? Which Batik version should I target for the GMF Runtime release for 2025-09?

[akurtakov]

Eclipse Platform also has 1.19 https://download.eclipse.org/eclipse/updates/4.37-I-builds/I20250811-1800/plugins/ so IMO it's best to update . As soon as no project contributes 1.18 or some project hard requires 1.19 Simrel will stop shipping 1.18.

[pcdavid]

Thanks for the quick reply. I've moved GMF Runtime back to 1.19.

[merks]

Yes, everyone should always use the latest.

Whomever is not doing that is the one who causes problems.

If everyone stops including 3rd party bundles in their features as required:

https://eclipse.dev/eclipse/markdown/?file=eclipse-simrel/.github/main/wiki/SimRel/Simultaneous_Release_Requirements.md#do-not-include-non-project-content-in-features

we'd be far less likely to have duplicates.

And it is in fact GMF that is causing the 1.18 version to be aggregated currently.

Could you stop including your 3rd party feature your "actual" feature such that it's no longer contributed to SimRel.

[pcdavid]

I think this should do it?
eclipse-gmf-runtime/gmf-runtime#96