| Summary: | Jubula persistence core makes use of deprecated EclipseLink / JPA OSGi API | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Technology] Jubula | Reporter: | Markus Tiede <markus.tiede> | ||||
| Component: | Core | Assignee: | Markus Tiede <markus.tiede> | ||||
| Status: | CLOSED FIXED | QA Contact: | Oliver Goetz <Oliver.Goetz> | ||||
| Severity: | critical | ||||||
| Priority: | P2 | CC: | Achim.Loerke | ||||
| Version: | 2.0 | ||||||
| Target Milestone: | 2.3 | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Markus Tiede
Switching to Gemini JPA would require some (maybe non-minor) code modifications due to limitations listed in bug 401785 Sorry - the one from comment 1 was closed as duplicate - bug 350516 is the original one. In addition to problems from comment 2 I'm currently running into bug 299636 as soon as I manually start die gemini bundle from the OSGi console and switch back to the UI application. Created attachment 230937 [details]
Current status of work for switching to Gemini JPA
@Triaged:? House keeping Comment on attachment 230937 [details]
Current status of work for switching to Gemini JPA
After discussion / analysis: Gemini seems to be no longer actively maintained and is not part of the official release train. Due to that we switch to a non-OSGi integration of EL in version 2.5.1
We've switched to EL 2.5.1 and JPA 2.1.0 with http://git.eclipse.org/c/jubula/org.eclipse.jubula.core.git/commit/?id=5bf058bd5f7b8dda1136939e6c86ee38d42a29be Please regression test properly and look for any side effects. Closed after talking to MMa (and MT). Since there have been no (negative) side effects we decided to close this ticket. |