According to the change logs of OpenJPA, JPA 3.1 should be included in the
OpenJPA 4.0.

https://issues.apache.org/jira/browse/OPENJPA-2908
---

Regards,

*Hantsy Bai*

Self-employed consultant, fullstack developer, agile coach,
freelancer/remote worker

GitHub: https://github.com/hantsy

Twitter: https://twitter.com/@hantsy
Medium: https://medium.com/@hantsy


On Sat, Dec 21, 2024 at 8:01 PM Richard Zowalla <r...@apache.org> wrote:

> Hi,
>
> please fill an issue regarding the JUnit 4 dependency (otherwise it
> might be forgotten).
>
> Most of the exception in the build are related to OpenJPA.
> OpenJPA does not implement JPA 3.1 and cannot deal with UUID fields.
> You either need to use Plume (with EclipseLink) or manually add
> Hibernate 6 for JPA 3.1 support.
>
> Classifier support should work in arquillian (at least we have it in
> our own build).
>
> Gruß
> Richard
>
>
> Am Samstag, dem 21.12.2024 um 11:26 +0800 schrieb hantsy bai:
> > I maintained a simple Jakarta EE 10 starter boilerplate project which
> > already worked in Glassfish, WildFly and OpenLiberty:
> >
> > https://github.com/hantsy/jakartaee10-starter-boilerplate
> >
> > Today I got the TomEE 10 release news and tried to add Arquillian
> > tomee-embedded and tomee-remote adapters to my project, but both
> > failed for
> > several exceptions.
> >
> > https://github.com/hantsy/jakartaee10-starter-boilerplate/pull/162
> >
> > I am not a professional for TomEE, and I am unsure how to fix them.
> >
> > There are some long-awaited problems still exist in the new version:
> > 1. tomee-embedded adapter still requires JUnit 4 dependency, else it
> > will
> > throw the class not found exception at runtime
> > 2. tomee-remote, although I set the `tomee.classifier` or
> > `tomee.remote.classifer` to `plus`, in the build, it always fected
> > the
> > `webprofile` archive.
> >
> > ---
> >
> > Regards,
> >
> > *Hantsy Bai*
> >
> > Self-employed consultant, fullstack developer, agile coach,
> > freelancer/remote worker
> >
> > GitHub: https://github.com/hantsy
> >
> > Twitter: https://twitter.com/@hantsy
> > Medium: https://medium.com/@hantsy
>
>

Reply via email to