Re: [eclipse-dev] Problems understanding osgi version resolving of org.a

[Wessel van Norel <delgurth@xxxxxxxxx>]

Hello Dirk and List,

Unfortunately it's the latter. I've totally missed the lack of a 1 in
front of the 9. That explains it and the problem can be found
somewhere between my keyboard and chair.

Thanks and sorry for the stupid question.

Kind regards,
Wessel van Norel

On Mon, Jun 29, 2026 at 5:10 PM Dirk Fauth <dirk.fauth@xxxxxxxxx> wrote:
>
> Hi,
>
> Either there is a typo or a misread. The dependency is on at least 1.9.1 and it resolves to 1.19.0
>
> 19 is more than 9. So that looks correct to me. The patch version doesn't even count here.
>
>
> Wessel van Norel via eclipse-dev <eclipse-dev@xxxxxxxxxxx> schrieb am Mo., 29. Juni 2026, 13:32:
>>
>> Hello Lars (and other readers),
>>
>> Unfortunately the publishing question was not my main question. I'm
>> mostly wondering how/why the eclipse osgi container accepts
>> 1.19.0.v20250506-1400 as a valid version for the constraint
>> Require-Bundle: org.apache.batik.css;bundle-version="[1.9.1,2.0.0)".
>> But I guess I need to find another example which is still in the
>> source code (hopefully there is none).
>>
>> Kind regards,
>> Wessel van Norel
>>
>>
>> On Fri, Jun 26, 2026 at 12:44 PM Lars Vogel via eclipse-dev
>> <eclipse-dev@xxxxxxxxxxx> wrote:
>> >
>> > Hi Wessel,
>> >
>> > I'm not involved with the Maven upload of the Eclipse artifacts, so I cannot answer your question.
>> >
>> > However, the Batik dependency is planned for removal in the next release. Our development build no longer uses it.
>> >
>> > Best regards, Lars
>> >
>> > On Thu, Jun 25, 2026 at 4:37 PM Wessel van Norel via eclipse-dev <eclipse-dev@xxxxxxxxxxx> wrote:
>> >>
>> >> 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
>> >> _______________________________________________
>> >> eclipse-dev mailing list
>> >> eclipse-dev@xxxxxxxxxxx
>> >> To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/eclipse-dev
>> >
>> >
>> >
>> > --
>> > Eclipse committer
>> > CEO vogella GmbH
>> >
>> > Haindaalwisch 17a, 22395 Hamburg
>> > Amtsgericht Hamburg: HRB 127058
>> > Geschäftsführer: Lars Vogel, Jennifer Nerlich de Vogel
>> > USt-IdNr.: DE284122352
>> > Fax (040) 5247 6322, Email: lars.vogel@xxxxxxxxxxx, Web: http://www.vogella.com
>> > _______________________________________________
>> > eclipse-dev mailing list
>> > eclipse-dev@xxxxxxxxxxx
>> > To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/eclipse-dev
>> _______________________________________________
>> eclipse-dev mailing list
>> eclipse-dev@xxxxxxxxxxx
>> To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/eclipse-dev