[tckrefactor] Jakarta Persistence 3.2 - JPQL new feature plus Persistence TCK runner and stored proc fixes #1247
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Another set of tests for new Jakarta Persistence 3.2. In this case it's about JPQL new features:
https://jakartaee.github.io/persistence/latest-nightly/nightly.html#jakarta-persistence-3-2
https://jakartaee.github.io/persistence/latest-nightly/nightly.html#a5587
There are two new improvements/fixes:
*persistence.sprocs.sql
Java package changes toCS_Procs
class to catch up last refactoring in the projectjpa/bin/pom.xml
to make it runnable like add missing dependencies, path fix and some refactor like version properties and put eclipselink part into Maven profileCC @lukasj @alwin-joseph @anajosep @arjantijms @cesarhernandezgt @dblevins @m0mus @edbratt @gurunrao @jansupol @jgallimore @kazumura @kwsutter @LanceAndersen @bhatpmk @RohitKumarJain @shighbar @gthoman @brideck @OndroMih @dmatej
@starksm64 @scottmarlow