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).
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
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.
My organization is using sonarqube:7.1 with sonar-bitbucket-plugin-1.2.3 (https://github.com/mibexsoftware/sonar-bitbucket-plugin) and everything is working fine. We are planning to upgrade to sonarqube:7.5 and while I was testing all the existing plugins, sonar-bitbucket-plugin is causing the issue(It's not supported in the newer version of Sonarqube). I want to upgrade to 7.5+ version of Sonarqube and want sonar-bitbucket-plugin as well. Could someone please help me out?
ERROR web[][o.s.s.p.Platform] Background initialization failed. Stopping SonarQube
java.lang.IllegalStateException: Fail to load plugin Bitbucket for Sonar [sonarbitbucket]
This community plugin was relying on the deprecated preview/issues analysis mode to analyze pull requests, that was finally removed.
Since SonarQube 6.7 the support of branches (and then pull requests) analysis has been properly integrated on the server side. Decorating PR was added progressively for various ALM, and for Bitbucket Server it is supported since 7.7.
Note that all branch/PR features are only available in commercial editions (or for free on SonarCloud for open source projects).
I ran into an issue today where my preview server was running an older version of a project instead of the most recently published version. The most recently published version was 1.0.4.10, but after some testing, I determined that version was not the version of the application that the server was retrieving.
After trying a few things, I tried publishing a new version under 1.0.5.0 instead of continuing with the 1.0.4.xx numbering, and that fixed the issue.
VS's auto increment feature recommended 1.0.4.10, but is there an issue with this being the same as 1.0.4.1? So maybe it was running 1.0.4.9? Or something behind the scenes I'm not aware of?
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.