Lukas Jungmann

@glassfishrobot Commented This issue was imported from java.net JIRA JPA_SPEC-9

> Since Jakarta EE 11 bumps the Java requirement to 21 this may be not true in the end eventually, there is a wish to stick with 17 and it...

It's targeted for v5

for 2.1.x/EE10 branch (will be created from master once 2.1.3 gets out) I'd keep it the way it is - the change from 8 could be perceived as incompatible by...

> If semver is followed to the letter No, it is not, updating min SE level is not being considered as a breaking change by EE (AFAIK)

* **Issue Imported From:** https://github.com/javaee/jpa-spec/issues/118 * **Original Issue Raised By:**@glassfishrobot * **Original Issue Assigned To:** @ldemichiel

@glassfishrobot Commented Reported by @lukasj

@glassfishrobot Commented pbenedict said: I am not a fan of @NamedEntityGraph because attribute string names (1) aren't typically discoverable by IDEs for refactoring and (2) are too far removed from...

@glassfishrobot Commented radcortez said: Seems a good idea, but it might harder to read which properties are loaded in each EntityGraph. I'm assuming, that a @NamedEntityGraphMember in a field property...

@glassfishrobot Commented This issue was imported from java.net JIRA JPA_SPEC-118