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
Related
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.
~We have some projects still running in AEM 6.1 SP2 (the move to newest version of AEM is in progress) and new projects in AEM 6.5.
AEM 6.1 runs in java 8 and AEM 6.5 runs in java 11.
For us developers this switching between jdk versions is difficult in our local environment, quite often we get our AEM instances corrupted or maven project imports are no longer working properly in IDE.
Anyone else had this situation? What are the best practices for such a situation?
My recommendation would be to set up vagrant box instances to your specs (AEM version + Java) and use automated deployments. This way, you can bring up a preconfigured instances in minutes by executing a single vagrant up command, run your automated deployment, and test your projects. If your instance gets corrupted, run a vagrant destroy command, bring up a new instance again with 0 configurations needed for the next deployment. You willincrease your productivity manifolds with this approach.
I have been using this approach for years and it has saved hours of devops work during critical project timelines
If you are using MAC [OSX], you can try Jenv. It can help you to have a unique Java Environment to a specific directory. We did find it very useful.
https://github.com/jenv/jenv
Thanks!
If you are running your AEM instances via shell scripts E.g. ./crx-quickstart/bin/start you can always specify the JAVA_HOME variable to be used in this particular file.
E.g.
export JAVA_HOME="path to your JVM"
export PATH=$JAVA_HOME/bin:$PATH
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 am trying to run spring sts tool eclpise. Installed java (jdk and jre) 8 but the runtime is still taken as 7. I get a pop up saying version is wrong and cant run the sts tool.
Kind Regards
In window / preferences / Installed JREs you need to have the JDK1.8 as the default set up.