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

[grgrzybek]

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.

[grgrzybek]

If accepted, it'd be nice to have jakarta.activation-api/1.2.3 released as well.

[lukasj]

at runtime, one has to use com.sun.activation:jakarta.activation artifact. The api one will be kind of broken in OSGi as well as on JPMS, since implementation classes, on which the API depends, are not available there. The only use-case for current API artifact is compile-time on JDK 8, or JDK 9+ if JPMS is not used (thus in classpath mode only)

[grgrzybek]

The fix applies both to the api (jakarta.activation:jakarta.activation-api) and full com.sun.activation:jakarta.activation) and the Require-Capability is what prevents from running any of the OSGi bundles on JDK8.

[grgrzybek]

To provide some background, this issue is one of similar issues created during my review of Eclipse-EE4J APIs:

• Update API jar OSGi manifest headers transactions#186
• Wrong OSGi relation between JCA 1.7 and JTA 1.3 (JavaEE8, JakartaEE8) connectors#120

[vaidsandeep]

should work by updating Require-Capability to
Require-Capability: osgi.ee;filter:="(&(osgi.ee=JavaSE)(version=1.8))"