You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Feb 23, 2023. It is now read-only.
While trying out Spring Native with @joshlong for Flowable we hit a problem when we had a dependency on spring-orm. We were bringing that dependency, but we don't need it during runtime, so we could proceed with our try out by excluding it.
In any case, I wanted to create this issue to shine light on the problem.
Perhaps this is not a Spring Native problem, but rather a GraalVM one.
========================================================================================================================
GraalVM Native Image: Generating 'demo'...
========================================================================================================================
[1/7] Initializing...
(3.8s @ 0.07GB)
Error: Cannot find org.springframework.orm.jpa.persistenceunit.DefaultPersistenceUnitManager.determineDefaultPersistenceUnitRootUrl, org.springframework.orm.jpa.persistenceunit.DefaultPersistenceUnitManager can not be loaded, due to javax/persistence/spi/PersistenceUnitInfo not being available in the classpath. Are you missing a dependency in your classpath?
Error: Use -H:+ReportExceptionStackTraces to print stacktrace of underlying exception
------------------------------------------------------------------------------------------------------------------------
0.2s (4.5% of total time) in 8 GCs | Peak RSS: 0.58GB | CPU load: 6.13
------------------------------------------------------------------------------------------------------------------------
The text was updated successfully, but these errors were encountered:
While trying out Spring Native with @joshlong for Flowable we hit a problem when we had a dependency on
spring-orm
. We were bringing that dependency, but we don't need it during runtime, so we could proceed with our try out by excluding it.In any case, I wanted to create this issue to shine light on the problem.
Perhaps this is not a Spring Native problem, but rather a GraalVM one.
I have created https://github.com/filiphr/spring-native-spring-orm-problem that can be run to see the problem.
The error outputted during the creation of the native image is:
The text was updated successfully, but these errors were encountered: