Is it possible to build the native Quarkus image under Java 16? Didn't find any instructions how to do it.
Somehow, it should be possible to do it because Oracle released GraalVM support for Java 16 (https://www.graalvm.org/release-notes/21_1/)
It should be possible (all you need to do is install the appropriate GraalVM version or the quay.io/quarkus/ubi-quarkus-native-image:21.1.0-java16 docker image) , but as of this time it is not part of our CI so your mileage may vary.
Related
I want to lean camunda-bpm. but now Requires jdk15 .But I can only have jdk8.
Can you teach me download history version for jdk8 ?
enter image description here
The CAMUNDA 7 RUN distribution requires only JRE 8+
https://docs.camunda.org/manual/7.17/installation/camunda-bpm-run/
CAMUNDA 8 is usually used containerized, so your local JRE version would not matter
I want to create a small binary out of my Compose desktop app. Following are the options out of the box with Compose:
Create native package with java runtime (great, but the size is very big)
Create an Uber (fat) Jar (but it requires Java 11 to run, since Compose library doesn't support older versions)
I believe it is be possible to convert the Uber Jar to native binary using GraalVM. I also tried running native-image command but it created an exe that in turn runs the Jar, which brings back to the same issue; Java 11 has to be installed on the machine. What am I missing?
Compose for desktop uses Swing in the background, so it is not fully compatible yet with GraalVM's native-image tool.
The latest version of GraalVM introduced experimental support for Swing on Linux, but it is still in development. Presumably once Swing support is stable, Compose should work with native-image.
What is happening in your example is that native-image fails to create the native executable, and instead creates a fallback image, which uses a regular JVM runtime.
I would like to run simple project generated from quarkus webpage and I am trying to run it on Linux with 19.3 GraalVM and JDK11. I know that the development of JDK11 support is still ongoing, but what version of GraalVM should I use then to test quarkus?
For Quarkus 1.0.x, you need to use GraalVM 19.2.1. You can download it from here: https://github.com/oracle/graal/releases/tag/vm-19.2.1 .
At the moment, we are working on two different fronts:
GraalVM 19.3 support. It's mostly working but we still have a number of critical issues due to GraalVM bugs and I'm not sure if we will ship with it or not. 1.1.0.CR1 is using 19.3 but I'm still not sure about the Final tbh.
GraalVM 19.3 + JDK 11 support: keep in mind that this is still preview on the GraalVM side. We are making slow progress on this as it comes with a new set of challenges. You can follow the progress here: https://github.com/quarkusio/quarkus/issues?q=is%3Aissue+is%3Aopen+label%3A%22GraalVM+%2B+Java+11%22 . We already made significant progress but as you can see we still have some issues to fix - some of them in Quarkus, some of them in GraalVM. Current planning is to have that one for January release (Quarkus 1.2).
I'm having problems executing Spring Tool, I get the error: Could not create the java virtual machine, and this in another window:
The error message isn't really explaining in detail what the problem is, but I would recommend to things here:
update to a recent JDK 1.8.0 (I think it is at 1.8.0_181 at the moment) and use that.
you can also specify the JVM to run STS in the STS.ini file in the same way than you could do that for plain Eclipse in the eclipse.ini file (described in more detail here: https://wiki.eclipse.org/Eclipse.ini).
It also looks like you are running a 64bit operating system, so in case you have a 64bit JDK installed, you should make sure to download and use the 64bit version of STS. From the error dialog it looks like you are trying to use the 32bit version of STS. You can do that, if you want to, but you would need to make sure that it picks up a 32bit JDK then. But I would strongly recommend to use a 64bit JDK together with the 64bit version of STS.
You better use JDK 1.8 etc. 1.6 is so old for starting new STS
I want to use Spark-Java 2.0 with Jetty 9.2. The trick here is that the Maven repository for Spark has dependency on jetty 9.0. The reason is that we already have working code using 9.2. When we bind/load the Spark jar at runtime there are class load errors.
The question is what issues may arise for Spark if I do a build to use jetty 9.2?
They other question could be, can I use excludes some how to load Jetty 9.2 over the 'requested' 9.0 classes? Is that possible, or will it cause me more bother?
Let me know if you think of other considerations. Also let me know where to find release notes for Jetty if you can? I looked for Jetty release notes here: Jetty Documentation hub; it is a little disappointing because they simply link to updated manuals. I look for Release Notes to show me what's different and changed between versions -- A new manual won't help unless I have a way to do 'diff' on the two manuals.
My thinking is that a jump between 9.0 to 9.2 should be a valid increment. My thanks in advance for your insights.