Merge Spring Data Envers into Spring Data JPA project

[mp911de]

JPA is a foundational technology for Envers and Envers is a specific enhancement to Hibernate. It makes sense to keep both projects colocated within the same repository for easier maintenance and dependency alignment.

[scordio]

Out of curiosity, will the JPA project become a multi-module, or will Envers classes be moved inside the JPA module?

I'm asking it because recently the auto-configuration for Envers has been added to Spring Boot with spring-projects/spring-boot@fbbfe6a and there is an ImportSelector that checks if org.springframework.data.envers.repository.config.EnableEnversRepositories is in the classpath.

If the JPA module contains Envers classes, Envers will always be auto-configured and I don't know if this is the behavior you would expect. Maybe the auto-configuration should be evaluated again (or dropped?)

[mp911de]

Spring Data JPA will become a multi-module project. From a consumer perspective, nothing is going to change, artifact Id's and the source separation will remain to not break downstream users.

[scordio]

Thanks for the clarification, @mp911de.

[schauder]

Done.