-
Notifications
You must be signed in to change notification settings - Fork 1.7k
The --no-fallback
option seems to be quietly enabling --allow-incomplete-classpath
#4010
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
Comments
@jamesward thanks for reporting the issue, we will check it out and get back to you |
@jamesward Getting error while using reproducer
|
Well that is not a useful error. Under the covers this task calls docker. Maybe you don't have docker installed? |
If this issue is still relevant in the latest GraalVM versions, please create a new issue for it and follow the template provided. Thank you |
Describe the issue
When I run native-image without
--no-fallback
on a project that has an incomplete classpath, it falls back (as expected). But when I add the--no-fallback
option the build does not fail and the resulting executable fails at runtime.Steps to reproduce the issue
git clone https://github.com/jamesward/scala3-graalvm-tester.git
cd scala3-graalvm-tester
--no-fallback
:./sbt packageWithFallback
--no-fallback
:./sbt packageWithNoFallback
Describe GraalVM and your environment:
Output when running with
--no-fallback
The text was updated successfully, but these errors were encountered: