Closed mustafashabib closed 4 years ago
Hi @mustafashabib ,
Thanks for the bug report. I hope to fix this issue once https://jira.spring.io/browse/DATAJPA-1497 is fixed.
BTW - some of the tests seem to be failing for your PR there, and also it seems to have merge conflicts now.
Yes I saw that, I will fix it asap ;)
The reference to the Spring Data JPA PR => https://github.com/spring-projects/spring-data-jpa/pull/305
Merge conflict fixed. Waiting to see if the build turns to green.
Looks like they removed the build step from their PRs. Just have to wait for review now.
The PR was rejected => https://jira.spring.io/browse/DATAJPA-1497
Hello @reda-alaoui
Any update about the rejected PR ? Will you try to convince them to accept it, or is there any workaround (except disabling illegal access) ?
I have been using your library for a few months and I really like it, it fits my needs perfectly :-) but if the support will stop with Java 12, I should unfortunately reconsider it for some of our projects :(
Thanks in advance !
Hello @jplumez ,
I am planning to retry convincing them. But I think the more we are, greater are the chances to convince them. So I hope you will let a comment on https://jira.spring.io/browse/DATAJPA-1497 or on https://github.com/spring-projects/spring-data-jpa/pull/305.
FYI, meanwhile, I think you can still permit illegal access with --illegal-access=permit
, even with JDK 12.
I have commented on the spring issue to add more support from users :)
https://github.com/spring-projects/spring-data-jpa/pull/305 was merged ! :champagne:
The first Spring Data JPA version to contain https://github.com/spring-projects/spring-data-jpa/pull/305 fix will be 2.3.0. Therefore the current issue fix will be available starting with spring-data-jpa-entity-graph
2.3.0
.
Spring Data JPA 2.3.0.RELEASE is now available. You can now fix the issue by:
and
Hi All
We're on gradle 5.1 and are seeing this message during builds using spring-data-jpa-entity-graph v2.07.
Just wanted to report it in case it's useful.