jakartaee / jakartaee/jaf-api

jakarta.activation-api 1.2.2 can't be used as OSGi bundle under JDK8

Open
#67 5 comments 0 reactions 0 assignees View on GitHub
Dominant language
Java
Stars
43
Forks
34
Avg merge
4d 3h
Merged PRs (30d)
2

Description

**Describe the bug**
jakarta.activation/jakarta.activation-api/1.2.2 contains this OSGi header:
```
Require-Capability: osgi.ee;filter:="(&(osgi.ee=JavaSE)(version=9.0))"
```

**To Reproduce**
Steps to reproduce the behavior:
1. Run Karaf under JDK8 `install -s mvn:jakarta.activation/jakarta.activation-api/1.2.2`
2. See error:
```
karaf@root()> install -s mvn:jakarta.activation/jakarta.activation-api/1.2.2
Bundle ID: 144
Error executing command: Error installing bundles:
Unable to start bundle mvn:jakarta.activation/jakarta.activation-api/1.2.2: org.osgi.framework.BundleException: Unable to resolve jakarta.activation-api [144](R 144.0): missing requirement [jakarta.activation-api [144](R 144.0)] osgi.ee; (&(osgi.ee=JavaSE)(version=9.0)) Unresolved requirements: [[jakarta.activation-api [144](R 144.0)] osgi.ee; (&(osgi.ee=JavaSE)(version=9.0))]
```

**Expected behavior**
jakarta.activation/jakarta.activation-api/1.2.2 is JPMS module, but the code itself doesn't require JDK9+. So this jar/bundle should be compatible with JDK8.

Contributor guide

Open the contributing guide

Research direction

Start by inspecting the OSGi manifest in jakarta.activation-api 1.2.2 and the build configuration that generates it. Reproduce the installation in Karaf under JDK8, then verify that the resulting bundle resolves without requiring JavaSE 9 while remaining compatible with the JPMS module.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
build-system
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.