Skip to content

[OPENJPA-3054] Fix OSGi/Karaf packaging after the switch to Jakarta - #250

Merged
cristof merged 2 commits into
masterfrom
OPENJPA-3054
Nov 2, 2026
Merged

cristof merged 2 commits into
masterfrom
OPENJPA-3054

Conversation

@rzo1

@rzo1 rzo1 commented Nov 2, 2026

Copy link
Copy Markdown
Contributor

Updates the openjpa bundle's Import-Package ranges to the Jakarta API versions and makes the app-server and logging imports optional, so the bundle resolves in OSGi. Rewrites the Karaf feature to use the Jakarta API bundles, and adds a karaf:verify step to the build so the feature's resolution is checked on every build.

Update the bundle's Import-Package ranges to the Jakarta API versions and
make app-server/logging imports optional, rewrite the Karaf feature with
the Jakarta API bundles, and run karaf:verify in the build.
@rzo1
rzo1 requested review from cristof and solomax November 2, 2026 09:44
…binary distribution

The lib dependencySet still listed the javax-era Geronimo spec jars, which
are no longer dependencies, so lib/ contained no persistence or transaction
API and openjpa.jar could not be used from the distribution. Include
jakarta.persistence-api and jakarta.transaction-api (required), keep
jakarta.jms-api, jakarta.validation-api and bval for the optional JMS and
Bean Validation integrations, and add derbyshared and derbytools which
Derby 10.16 needs next to derby.jar.

Update LICENSE and NOTICE of the distribution and of openjpa-all for the
bundled Jakarta API jars (EPL-2.0) and drop entries for jars no longer
shipped. Set the openjpa-all Specification-Version to 3.2.
@cristof
cristof merged commit bf85c0b into master Nov 2, 2026
4 checks passed
@cristof
cristof deleted the OPENJPA-3054 branch November 2, 2026 22:14
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.

3 participants