Switch from org.eclipse.swt to org.eclipse.platform

[mkurz]

No need to self host under your internal-repo https://apps.egiz.gv.at/maven/org/eclipse/swt/

Background:
While getting PDF-Over working on Linux aarch64, the build failed, complaining that the org.eclipse.swt.gtk.linux.aarch64 artifact can not be fetched. Turns out that neither on

• your internal maven repo https://apps.egiz.gv.at/maven/org/eclipse/swt/
• nor on maven central https://repo1.maven.org/maven2/org/eclipse/swt/

the linux aarch64 classifier exists (and Maven central does not even host new releases of swt under that groupid...).

So I was looking around on https://eclipse.dev/eclipse/swt/ and https://github.com/eclipse-platform/eclipse.platform.swt and the maven coordinates where they say they host the swt artifacts is org.eclipse.platform under https://repo1.maven.org/maven2/org/eclipse/platform/.

And indeed its there, they even publish aarch64 artifacts:

The only thing that made me wonder is the versioning: Currently in PDF-Over you depend on version 4.35 from the org.eclipse.swt groupid, but in org.eclipse.platform all versions are on 3.x

Turns out there is this very interesting post:

• SWT 4.x versions on Maven Central eclipse-platform/eclipse.platform.swt#1370

So reading the replies, my understanding is that the artifacts they publish on maven central under the org.eclipse.platform should be just the same like the ones you can download from the website (here at the bottom swt 4.38) or from the archives (like the 4.35 one).

So lets check this:
From https://archive.eclipse.org/eclipse/downloads/drops4/R-4.35-202502280140/ download the swt-4.35-gtk-linux-x86_64.zip file and unpack it and also unpack the swt.jar file inside it.
Turns out version 4.35 was released in March 2025 (see its git tag), we therefore download version 3.129.0 of the org.eclipse.platform groupid, as it was published around the same time: https://repo1.maven.org/maven2/org/eclipse/platform/org.eclipse.swt.gtk.linux.x86_64/3.129.0/ - again unpack the jar.
If you now compare the contents of the two unpacked jar files, you will see that they are 99% the same (talking about byte comparison, not just doing ls or tree), just the manifest files differ slightly and some property files got removed - I guess this was some cleanup task.
But anyway, this shows that we can just replace 4.35 with 3.129.0.
And even more: If you download the jar from your internal repo (https://apps.egiz.gv.at/maven/org/eclipse/swt/org.eclipse.swt.gtk.linux.x86_64/4.35/) and compare its content with the two other jars, you will again see the content is 99% the same, except the manifest and some cleaned up property files (again, just like before).

Therefore I am very confident we can just switch the groupId to org.eclipse.platform and the 3.x versioning, which gives us the benefits of

• Not needing to take care of self hosting (no maintenance cost)
• Having all the classifiers of the artifact available (like aarch64)

[mkurz]

Forgot: To upgrade, you can always just check what's the latest version listed here: https://repo1.maven.org/maven2/org/eclipse/platform/org.eclipse.swt.gtk.linux.x86_64/maven-metadata.xml which currently is 3.132.0.