eclipse-ee4j / eclipse-ee4j/jersey
jaxrs-ri OSGI import-package on org.glassfish.hk2.osgiresourcelocator seems incorrect.
- Dominant language
- Java
- Stars
- 730
- Forks
- 382
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
Looking at import-package generated in the `MANIFEST.MF` for `jaxrs-ri`. I think the following jaxrs-ri import-package is not correct: `org.glassfish.hk2.osgiresourcelocator {version=[2.5,4)}`
It's actually caused by this clause: `${hk2.osgi.version}`, which refer to: `org.glassfish.hk2.*;version="[2.5,4)"`
But `org.glassfish.hk2.osgiresourcelocator` is not following same versioning as other `org.glassfish.hk2` projects. Also according to repacked bundles that are declaring it, they are declaring it as dynamic import, for example:
from: `jakarta.xml.bind-api:2.3.3`
```
!org.glassfish.hk2.osgiresourcelocator,
javax.activation;version=!,
*
org.glassfish.hk2.osgiresourcelocator
```
Or it's not matching the expected verson, from jersery-common:2.47: `org.glassfish.hk2.osgiresourcelocator {version=[1.0,2)} `
I will try to provide a PR for this.
Best regards,
Kevan.
Contributor guide
Research direction
Start by tracing the `${hk2.osgi.version}` configuration that generates the jaxrs-ri `MANIFEST.MF` Import-Package entry. Compare the generated range for `org.glassfish.hk2.osgiresourcelocator` with the ranges shown for repacked bundles and jersey-common; done means the generated import matches the package's expected versioning.
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