Skip to content

[SPI-FLY] Add Java 25 to workflow matrix#813

Open
stbischof wants to merge 1 commit intoapache:trunkfrom
stbischof:patch-1
Open

[SPI-FLY] Add Java 25 to workflow matrix#813
stbischof wants to merge 1 commit intoapache:trunkfrom
stbischof:patch-1

Conversation

@stbischof
Copy link
Copy Markdown

@stbischof stbischof commented Apr 2, 2026

@alien11689

The SPI Fly Framework Extension currently does not work with JDK 25. The root cause appears to be the included ASM dependency, which is not compatible with JDK 25.

There is already a Dependabot pull request that upgrades ASM to a newer, compatible version, and it has been merged. However, no new SPI Fly release has been published since then, so the issue persists for users relying on official releases.

As a comparison, the Dynamic Bundle works correctly on JDK 25 when updating the ASM dependency manually. This workaround is not applicable to the Framework Extension, as it bundles the ASM dependency internally and cannot be easily overridden.

Request:
Please publish a new release of SPI Fly that includes the updated ASM version so the Framework Extension can be used with JDK 25.

The JDK 25 Job fails because of bnd version < 7.2

@alien11689
Copy link
Copy Markdown
Contributor

Hi @stbischof
to upgrade to the new bnd 7.x we need to drop support for Java < 17. At least in spi-fly.

We wanted to have support for Java 11 as the minimal (but now we have still Java 8 available) then I think we could release current spi-fly as 1.4.0. And immediatelly start working on 2.0.0 release with minimal Java 17 for the spi-fly.
Other Aries modules are completely separated.

@jbonofre WDYT?

@stbischof
Copy link
Copy Markdown
Author

stbischof commented Apr 2, 2026

There ist no conflict between bnd 7 and jdk <17

You can use jdk 17 or 21 or 25 and Compile target ist still java 8.

It is absolutly fine if you keep java 8 support

@alien11689
Copy link
Copy Markdown
Contributor

@stbischof I will take a look on the spi-fly configuration - meantime please feel free to update your PR to reflect your needs.

@alien11689
Copy link
Copy Markdown
Contributor

@stbischof you can take a look at my draft PR #815

I was not able to force bnd to generate manifests for JavaSE=1.8 - the minimal is always JavaSE=17 no matter what I say via -ee.

The reason is probably that spi-fly artifacts has the dependency on bnd artifacts which sets the JavaSE=17 and bnd takes max of JavaSE from bundles ignoring what I say in java target version.

@stbischof
Copy link
Copy Markdown
Author

stbischof commented Apr 2, 2026

I will look on that tomorrow!

For now. Use 2 Versions of bnd.

6.4 ish for aqute and bndlib.
7.2 ish for bnd-maven-plugin.

And stay at compile target 8

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants