Design/552 - Move JPA to Jakarta Persistence #775
Conversation
maho7791
commented
Oct 26, 2024
- Changed Service API to Jakarta
- Changed Spec-Text
- renamed project from jpa to jakartapersistence - moved package from javax to jakarta - modified spec version - modified spec names - modified property names corresponding to new java spec Signed-off-by: Mark Hoffmann <[email protected]>
- renamed Java EE to Jakarta EE - renamed javax to jakartapersistence - renamed JPA tp Jakarta Persistence - tried to refer to Version 3.0, 3.1, 3.2 Signed-off-by: Mark Hoffmann <[email protected]>
timothyjward
left a comment
There was a problem hiding this comment.
Some minor changes needed related to the chapter number and Jakarta versions we support.
I’m happy with the rename, but there are ongoing discussions in #552 (comment)
- Looked over properties - fixed issues from PR Signed-off-by: Mark Hoffmann <[email protected]>
laeubi
left a comment
There was a problem hiding this comment.
I think wee need to adapt (or copy?) the TCK as well.
|
The TCK will follow |
Great it would be good to handle the following TCK issues along with that:
Also the last API package is currently a bit unusable we should account for this as well There are also some open request for enhancements that would be great to incooperate them in the new spec (they are actually de-facto implemented by aries and pax implementation):
|
|
@maho7791 any updates here? |
|
@maho7791 could you please give us an update on your work on the next spec call? |
|
As asked in the spec call the other impl is: https://github.com/ops4j/org.ops4j.pax.jpa |