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
it fails at runtime with UnsupportedFeatureError: Unresolved element found (a bit like #511 but different I think). You can work around it by doing a check for Class.forName("com.acme.NonExistentClass") before trying isAssignableFrom() it. Seems wrong, because a normal JVM behaves differently.
The text was updated successfully, but these errors were encountered:
Ping on this. I found another instance of this in Spring Boot (in addition to the two above). If Graal could just throw NoClassDefFoundError like a normal VM it would make these code paths work as expected. Is there any reason not to do that?
We have a new, experimental flag: --allow-incomplete-classpath which should take care of cases like this. You can try it by building GraalVM from source. This will be available in the next release, rc10.
If you build a native image with
--report-unsupported-elements-at-runtime
from code that does this:it fails at runtime with
UnsupportedFeatureError: Unresolved element found
(a bit like #511 but different I think). You can work around it by doing a check forClass.forName("com.acme.NonExistentClass")
before tryingisAssignableFrom()
it. Seems wrong, because a normal JVM behaves differently.The text was updated successfully, but these errors were encountered: