You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not familiar with hibernate-jpa, but maybe you can simply switch to the jakarta dependencies instead or at least set the scope of that dependency to "provided"?
The text was updated successfully, but these errors were encountered:
This is probably caused by jOOQ itself, see jOOQ/jOOQ#9641. You should be able to exclude jOOQ's transitive dependency to prevent that API from leaking onto your classpath?
For the record, jOOQ/jOOQ#9641 has been implemented in jOOQ 3.16 and will ship soon (by the end of 2021, hopefully). After that, we'll have only Jakarta dependencies, no javax dependencies from the deprecated Java EE APIs anymore.
I've included this dependency into my project and noticed errors in my code, as for example the
javax.persistence.Query.getResultStream()
method was not found anymore.It seems this dependency is using an old Hibernate JPA dependency from 2013!!
https://mvnrepository.com/artifact/org.hibernate.javax.persistence/hibernate-jpa-2.1-api
I'm not familiar with hibernate-jpa, but maybe you can simply switch to the jakarta dependencies instead or at least set the scope of that dependency to "provided"?
The text was updated successfully, but these errors were encountered: