[eclipse-dev] Problems understanding osgi version resolving of org.apach

[Wessel van Norel <delgurth@xxxxxxxxx>]

Hello,

First of all I'm not sure if this is the right place to address this
issue, but I didn't see a mailing list for eclipse-platform so that's
why I'm using this mailing list.

I'm currently in the process of building an eclipse application trying
to use only maven (central) repository dependencies and no p2 usage
(don't ask me why, it's what I'm asked to do).

While doing this something around the versioning of
org.apache.batik.css strikes me as incorrect and I'm wondering how /
why it's currently working. The good news is that Lars Vogel seems to
have removed this dependency all together for eclipse 2026-09 with
this pull request:
https://github.com/eclipse-platform/eclipse.platform.ui/pull/4092

But before he removed the dependency it was listed as:

https://github.com/eclipse-platform/eclipse.platform.ui/blob/132e20a724e1f0cc0da5c06e64075b78f430c4b9/bundles/org.eclipse.e4.ui.css.core/META-INF/MANIFEST.MF#L42

Require-Bundle: org.apache.batik.css;bundle-version="[1.9.1,2.0.0)",

The problem I've is with the required patch version, which seems to be
satisfied with a non .1 patch version?

>From the installable unit index report:
https://download.eclipse.org/releases/2026-06/202606101000/buildInfo/archive/download.eclipse.org/releases/2026-06/202606101000/index/org.eclipse.e4.ui.css.core_0.14.700.v20260516-1214.html

 <required namespace="osgi.bundle" name="org.apache.batik.css"
range="[1.9.1,2.0.0) ◢ ➥1.19.0.v20250506-1400"/>

How does 1.19.0.v20250506-1400 satisfy 1.19.1?

This feals incorrect to me, certainly since the batik-css bundle
itself publishes itself as 1.9.0 on the package level:
https://download.eclipse.org/releases/2026-06/202606101000/buildInfo/archive/download.eclipse.org/releases/2026-06/202606101000/index/org.apache.batik.css_1.19.0.v20250506-1400.html

Now, as I said, for this dependency this is no longer a problem since
it's removed. But this might happen with other dependencies as well?

Another unrelated remark. Many (perhaps all, I didn't check this) of
the eclipse project's MANIFEST.MF files published on maven central
contain the following information:

Bundle-Name: %pluginName
Bundle-Vendor: %providerName

For example the bundle that contains this batik-css requirement:
https://mvnrepository.com/artifact/org.eclipse.platform/org.eclipse.e4.ui.css.core/0.14.700

Not really important, but perhaps it's easy to fix for someone who
knows how this publishing is done?

Kind regards,
Wessel van Norel