-
Notifications
You must be signed in to change notification settings - Fork 63
Maven example with standalone jar #18
Comments
If what you want to achieve is to have one single jar you can run, that's not really possible if you want to have compilation enabled with graal, since you need to update the module path. |
Very curious about this, too. Why can Taking this project as an example,
So why can't I do
Or (basically identical to the maven exec):
Is there something simple I am missing? Thank you! |
I'm not quite sure what you are asking but I'll take a crack and answering what I think you are asking so please let me know if I'm missing the mark. The first example you gave cannot work since The problem with your second example (also with the first one) is that the built jar does not have a proper manifest to be executed with |
Thank you for checking in! Let me add some clarity for my use-case. I'm trying to run a fat Spring Boot JAR in Docker, which can run some JavaScript too. Today CMD java -jar /opt/foo/mySpringBoot.jar I did end up getting a new stacktrace when I used So perhaps I just need to wait for the next release. Example + trace@SpringBootApplication
public class Application {
public static void main(String[] args) {
try(Context context = Context.newBuilder("js").build()) {
context.eval("js", "print('Hello from JS!');");
}
SpringApplication.run(Application.class, args);
}
|
I'm wondering if it's possible to information on how to include the dependencies required to run this sample with a standalone jar.
The text was updated successfully, but these errors were encountered: