Update Spring APIs to Spring Boot 3

[aureamunoz]

Highlight overview

This pull request primarily includes cosmetic changes, such as renaming methods and reorganizing packages. However, it also features significant refactoring of the quarkus-spring-data-rest-extension to align with the latest spring-data-jpa 3.x updates.

Key Changes in spring data jpa latest version:

Introduction of New Interfaces:

• With spring-data-jpa 3.x, two new interfaces, ListCrudRepository and ListPagingAndSortingRepository, were introduced. These interfaces return List<T> types, unlike the existing PagingAndSortingRepository and CrudRepository, which return Iterable<T>.
• The class hierarchy has been modified as follows:

• PagingAndSortingRepository no longer extends CrudRepository.
• ListCrudRepository extends CrudRepository.
• ListPagingAndSortingRepository extends PagingAndSortingRepository.
• JpaRepository extends both ListCrudRepositoryand ListPagingAndSortingRepository.

Refactoring of spring-data-rest Extension:

• To accommodate these changes, the extension's hierarchy was restructured. Rather than maintaining different implementors, a single implementor now checks the repository type and implements the corresponding methods.
• All logic is consolidated in the RepositoryMethodsImplementor, which implements all repository methods based on the repository type.
• The SpringDataRestProcessor has been updated to include the new interfaces and now performs registration in a unified method (registerRepositories) instead of using two separate methods.
• Unification of PropertiesProvider Classes: these classes have been unified to incorporate the new methods from the List***Repository interfaces.
• Updates to EntityClassHelper: the EntityClassHelper has been relocated and now includes new methods used by RepositoryMethodsImplementor to detect the repository type for implementation.
• Modifications to Tests: the Paged***Test no longer checks methods inherited from Crud**Repos. A new test case, CrudAndPagedResourceTest, has been added for a repository extending both Crud and Paged repositories.

Note:
The new List**** methods are not specifically exposed via REST, as this is consistent with Spring's behavior.

Additionally, I plan to clean up some comments in the code. I will address these and any other changes based on your feedback during the review.

[aureamunoz]

cc @geoand

[geoand]

Thanks for this.

The CI failures definitely seem related to the PR

[aureamunoz]

Thanks for this.

The CI failures definitely seem related to the PR

Oh, absolutely. I will take a look

[aureamunoz]

This is off to a good start, so could you, @geoand take a look as soon as you have some time available?

[geoand]

Sure, I'll try take and take a look tomorrow

[geoand]

A high level overview of the changes in the description of the PR would be nice for future reference.

[geoand]

A high level overview of the changes in the description of the PR would be nice for future reference.

I would also like to know why there are new implementors. Please add this information to the description of the PR

[aureamunoz]

A high level overview of the changes in the description of the PR would be nice for future reference.

I would also like to know why there are new implementors. Please add this information to the description of the PR

Yes, sure. It's in progress.

[michalvavrik]

@geoand I added breaking-change, not sure why you removed it but this is super breaking. for example it breaks compilation due to The class hierarchy has been modified: PagingAndSortingRepository no longer extends CrudRepository as written in description. it already broke QE project and if compilation is broken, it must be documented. Please add note to the migration guide.

[gsmet]

@michalvavrik I added the description to the migration guide for 3.12.

[gsmet]

Thanks for your vigilance BTW!

[michalvavrik]

thank you @gsmet . BTW I have 4 failures after this PR got merged. I didn't use Spring for 3 years, so my knowledge is limited, so it could be false alarm. Anyway, it feels like a bug so I'll open issues within one hours.

[gsmet]

@michalvavrik you can create them tomorrow. We still have a week before the Core Final.

[geoand]

Thanks.

I removed it by mistake

[jedla97]

The class hierarchy has been modified: PagingAndSortingRepository no longer extends CrudRepository. Instead, JpaRepository now extends both CrudRepository and PagingAndSortingRepository.

Reading this I'm not sure if it's correct. JpaRepository is now extended by ListCrudRepository and ListPagingAndSortingRepository. Yes ListCrudRepository is extended by CrudRepository but JpaRepository is not directly extend CrudRepository.

Not sure if this should be updated in migration guide.

[aureamunoz]

The class hierarchy has been modified: PagingAndSortingRepository no longer extends CrudRepository. Instead, JpaRepository now extends both CrudRepository and PagingAndSortingRepository.

Reading this I'm not sure if it's correct. JpaRepository is now extended by ListCrudRepository and ListPagingAndSortingRepository. Yes ListCrudRepository is extended by CrudRepository but JpaRepository is not directly extend CrudRepository.

Not sure if this should be updated in migration guide.

It's the opposite, I improved the description here. Take a look and let me know if it's clearer @jedla97

[aureamunoz]

A new PR fixing the #41134 , #41135 and #41136 is coming but it needs a quarkus-spring-data-api release to be done (PR#14)
cc @michalvavrik @jedla97

[michalvavrik]

Cool, thanks!

[jedla97]

@aureamunoz Thanks for working on this and thanks for update.

It's much more clearer. I know what's happend after reading it and don't need to deep dive how it changed.

Probably one thing is it should be also updated in https:/quarkusio/quarkus/wiki/Migration-Guide-3.12