-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add native support for Envers #2662
Comments
@ch4mpy Thanks for creating the issue! I've created oracle/graalvm-reachability-metadata#82 to provide missing metadata for hibernate-envers. Once that's in place we will continue here with the missing bits from data spring-data side. |
Hi! Is this issue still in progress? The metadata issue in the graalvm repo seems to be closed and afaik this issue here can be unblocked :) |
Any news regarding this? |
Any updates on this? There are services we would like to migrate into spring-native to reduce resource foot prints but almost all of our services are depending on envers. I honestly don't want to reinvent the wheel and implement my own solution for basic auditing needs. A small heads up would be sufficient about the progress, so we can have our own timelines regarding the progress :) |
We'd also like our existing services to use native images, but this issue is a blocker for us. Has there been any progress on it? |
Hi, do you have any update on this ? |
As requested by @snicoll , I'm moving this issue here.
It would be great to have a complete working sample with an
@Audited
@Entity
associated with aRevisionRepository
in an application with@EnableEnversRepositories
, and having instruction to build a native image (that successfully runs).I created a minimal spring-boot 3 application (using latest SNAPSHOT) with
@Audited @Entity
RevisionRepository
@RestController
Native image was build on windows with Graalvm 22.2.0 and x64 native build tools command prompt with
mvnw -Pnative build
This app runs fine in the JVM, but native image won't start with
The text was updated successfully, but these errors were encountered: