paulrutter commented on PR #433: URL: https://github.com/apache/felix-dev/pull/433#issuecomment-6076515013
Matrix is `[17,21,25]` — 23 dropped as discussed, and **27 taken back out**. 27 does fail, but not in anything this PR touches. Aries SpiFly 1.3.7 bundles ASM 9.6, which rejects class file major version 71, so its weaving hook throws for every class it sees and Jetty never finishes starting: ``` org.apache.aries.spifly.dynamic.bundle [Events.Framework] ERROR : FrameworkEvent ERROR java.lang.ClassFormatError: Weaving hook failed. Caused by: java.lang.IllegalArgumentException: Unsupported class file major version 71 ``` `JettySniHostCheckIT` then waits 30 seconds for an `HttpService` that never registers. Not SNI or TLS specific — the test keystore is fine and Jetty 12.1.14 starts normally up to that point. SpiFly 1.3.8 carries ASM 9.10.1, which does declare `V27 = 71`, but it is not drop-in: bumping it alone leaves the test container with unresolved bundles, because its `Import-Package` changed. So it needs real work in the HTTP module rather than a version bump here. While digging I also found that the Felix HTTP ITs pin `org.apache.felix.framework` **7.0.5** in `http/jetty12/pom.xml`, so pax-exam always runs them against the released 2022 framework rather than the one built in the reactor — visible in the IT logs, which attribute warnings to `~/.m2/.../7.0.5/...` rather than `framework/target/classes`. That explains why this was not caught earlier: those ITs are not wired to the rest of the build. Both are filed as [FELIX-6869](https://issues.apache.org/jira/browse/FELIX-6869). Once the first part lands, 27 can go back in the matrix. For the record, the framework itself is fine on 26 and 27 — both green including the OSGi Core R8 TCK, checked on the plurl branch where the path filters build only `framework` and `framework.tck` ([run](https://github.com/apache/felix-dev/actions/runs/37604709102)). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
