Re: Heads up: broken OSGi Bundle-version in debian package jar file MANIFEST.MF

[Emmanuel Bourg <ebourg@apache.org>]

Hi,

Thank you for spotting this issue. The build expects a gradle.property 
file with a 'release' property to disable the -SNAPSHOT suffix.

This is now fixed in asm/9.8-2

Emmanuel Bourg


On 19/10/2025 10:00, Steinar Bang wrote:
> Today I reported the following bug on libasm-java 9.8-1
>   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1118387
>
> The problem is that the MANIFEST.MF header Bundle-version looks like
> this:
>   Bundle-version: 9.8-SNAPSHOT
> and this causes the asm jar file to fail when being loaded as an OSGi
> bundle.
>
> This indicates two things:
>   1. The debian package may not actually be built from the git tag
>      matching the release
>   2. Whatever creates the OSGi headers of MANIFEST.MF doesn't handle
>      SNAPSHOT releases correctly (eg. the apache felix maven-bundle-plugin
>      would have created the header "Bundle-version: 9.8.SNAPSHOT" which
>      would have loaded correctly in OSGi)
>
> And the reason I'm writing here as well as reporting the bug is that
> this could affect other debian java library packages with OSGi headers
> in their MANIFEST.MF files.
>
> (It may be that not many others care about OSGi these days... but I
> do... :-) )
>
> If someone run into problems trying to fix OSGi headers in debian java
> library packages I am willing to assist.