In November 2019, I attended Devoxx Belgium together with other AMIS colleagues. The yearly gathering of over 3000 Java developers (numbers provided by Devoxx website) were Java and software development are the core themes.

At Devoxx, among other things, I learned about Quarkus and wanted to know more about it.

In this article I will share with you the steps I took, to set up a demo environment, so I could get started with Quarkus.

Quarkus

A Kubernetes Native Java stack tailored for OpenJDK HotSpot and GraalVM, crafted from the best of breed Java libraries and standards.
_{[https://quarkus.io/]}

Container first
From the outset Quarkus has been designed around a container first philosophy. What this means in real terms is that Quarkus is optimised for low memory usage and fast startup times in the following ways:

First Class Support for Graal/SubstrateVM
Substrate support has been an important part of the design for Quarkus from the beginning. When an application is compiled down to a native image it starts much faster and can run with a much smaller heap than a standard JVM. Quarkus are all tested in Substrate, and can run without the -H:+ReportUnsupportedElementsAtRuntime flag.
Build Time Metadata Processing
As much processing as possible is done at build time, so your application will only contain the classes that are actually needed at runtime. In a traditional model all the classes required to perform the initial application deployment hang around for the life of the application, even though they are only used once. With Quarkus they are not even loaded into the production JVM. This results in less memory usage, and also faster startup time as all metadata processing has already been done.
Reduction in Reflection Usage
As much as possible Quarkus tries to avoid reflection, reducing startup time and memory usage.
Native Image Pre Boot
When running in a native image Quarkus pre-boots as much of the framework as possible during the native image build process. This means that the resulting native image has already run most of the startup code and serialized the result into the executable, resulting in even faster startup.

_{[https://quarkus.io/vision/container-first]}

Unifies imperative and reactive
Combine both the familiar imperative code and the non-blocking reactive style when developing applications.

For years, the client-server architecture has been the de-facto standard to build applications. But a major shift happened. The one model rules them all age is over. A new range of applications and architecture styles has emerged and impacts how code is written and how applications are deployed and executed. HTTP microservices, reactive applications, message-driven microservices and serverless are now central players in modern systems.

Quarkus has been designed with this new world in mind, and provides first-class support for these different paradigms. Quarkus development model morphs to adapt itself to the type of application you are developing.
_{[https://quarkus.io/vision/continuum]}

Developer joy
A cohesive platform for optimized developer joy:

Unified configuration
Zero config, live reload in the blink of an eye
Streamlined code for the 80% common usages, flexible for the 20%
No hassle native executable generation

Best-of-breed libraries and standards
Quarkus provides a cohesive, fun to use, full-stack framework by leveraging a growing list of over fifty best-of-breed libraries that you love and use. All wired on a standard backbone. Learn more about Quarkus Extensions.
_{[https://quarkus.io/vision/standards]}

Quarkus is open. All dependencies of this project are available under the Apache Software License 2.0 or compatible license.
_{[https://quarkus.io/]}

Quarkus at Devoxx Belgium 2019

Below, you can see the sessions about Quarkus at Devoxx Belgium 2019:

Birds of a Feather (Informal evening sessions of one hour, where like minded people get together and discuss technology):

“Quarkus Community BOF” by Georgios Andrianakis, Dimitris Andreadis, Emmanuel Bernard, Kamesh Sampath (Server Side Java)

Conference (Tech sessions of 50 minutes on a range of different technologies, practices and methodologies):

“Kubernetes Native Spring apps on Quarkus” by Georgios Andrianakis (Server Side Java)
_{[https://www.youtube.com/watch?v=9wJm8g83vqA]}
“Quarkus why, how and what” by Emmanuel Bernard (Server Side Java)
_{[https://www.youtube.com/watch?v=SQDR34KoC-8]}

By the way, my colleague Lucas Jellema, wrote an article with the title “The state of Java [developers] – reflections on Devoxx 2019”.
_{[https://technology.amis.nl/2019/11/11/the-state-of-java-developers-reflections-on-devoxx-2019/]}

Please see https://devoxx.com/#/ for more information about Devoxx events, also in other places in the world.

And I also wanted to mention that Devoxx Belgium 2020 is canceled.
Devoxx should be a place of joy, socialising and fun… not a place where people are afraid of getting infected. As a result we decided to cancel this years edition of Devoxx Belgium.

The next Devoxx Belgium is scheduled November 8th – 12th 2021.
_{[https://devoxx.be/]}

GraalVM

GraalVM is a high-performance runtime that provides significant improvements in application performance and efficiency which is ideal for microservices. It is designed for applications written in Java, JavaScript, LLVM-based languages such as C and C++, and other dynamic languages. It removes the isolation between programming languages and enables interoperability in a shared runtime. It can run either standalone or in the context of OpenJDK, Node.js or Oracle Database.
_{[https://www.graalvm.org/getting-started/]}

Quarkus – get started

Quarkus - Supersonic Subatomic Java, setting up a demo environment using Vagrant and Oracle VirtualBox lameriks 2020 08 2

In order to get started with Quarkus, there are some steps to be taken as can be seen in the picture above.
_{[https://quarkus.io/get-started/]}

As I did before, on my Windows laptop, I wanted to use a demo environment within an Oracle VirtualBox appliance, with the help of Vagrant.

Based on the Quarkus guides I wanted to try out, I knew I also was going to need Kubernetes.
_{[https://quarkus.io/guides/deploying-to-kubernetes]}

So, again I created a demo environment with K3s (with the Kubernetes Dashboard) on top of an Ubuntu guest Operating System within an Oracle VirtualBox appliance, in a similar way I described in a previous article.
_{[ https://technology.amis.nl/2020/01/15/rapidly-spinning-up-a-vm-with-ubuntu-and-k3s-with-the-kubernetes-dashboard-on-my-windows-laptop-using-vagrant-and-oracle-virtualbox/]}

Once I had that up and running, I would extend it with the software mentioned in the steps above. But more about that, later on in this article.

For K3s (lightweight certified Kubernetes distribution) this time I wanted to use the Docker container runtime instead of containerd.

I had a look at the K3s documentation and found I had to do the following:

Install Docker on the K3s node. One of Rancher’s Docker installation scripts can be used to install Docker:
curl https://releases.rancher.com/install-docker/19.03.sh | sh
Install K3s using the –docker option:
curl -sfL https://get.k3s.io | sh -s – –docker
Confirm that the cluster is available:
$ sudo k3s kubectl get pods –all-namespaces
Confirm that the Docker containers are running:
$ sudo docker ps

_{[https://rancher.com/docs/k3s/latest/en/advanced/#using-docker-as-the-container-runtime]}

I also wanted to be able to use Docker as a non-root user.
_{[https://docs.docker.com/engine/install/linux-postinstall/#manage-docker-as-a-non-root-user]}

So, based on the steps mentioned above, in the scripts directory I changed the content of the file k3s.sh to:

#!/bin/bash
echo "**** Begin installing k3s"

#Install
curl https://releases.rancher.com/install-docker/19.03.sh | sh
curl -sfL https://get.k3s.io | K3S_KUBECONFIG_MODE="644" sh -s - --docker

# Wait 2 minutes
echo "**** Waiting 2 minutes ..."
sleep 120

#List nodes
echo "**** List nodes"
kubectl get nodes
echo "**** List pods"
sudo k3s kubectl get pods --all-namespaces
echo "**** List Docker containers"
sudo docker ps

#use Docker as a non-root user
sudo usermod -aG docker vagrant

echo "**** End installing k3s"

In my existing demo environment, created when I wrote a previous article , I changed the content of the Vagrantfile to:
_{[https://technology.amis.nl/2020/01/15/rapidly-spinning-up-a-vm-with-ubuntu-and-k3s-with-the-kubernetes-dashboard-on-my-windows-laptop-using-vagrant-and-oracle-virtualbox/]}

Vagrant.configure("2") do |config|
  config.vm.box = "ubuntu/bionic64"
  
  config.vm.define "ubuntu_k3s" do |ubuntu_k3s|
  
    config.vm.network "forwarded_port",
      guest: 8001,
      host:  8001,
      auto_correct: true
      
   config.vm.network "forwarded_port",
      guest: 8080,
      host:  8080,
      auto_correct: true
      
   config.vm.network "forwarded_port",
      guest: 8090,
      host:  8090,
      auto_correct: true
      
    config.vm.provider "virtualbox" do |vb|
        vb.name = "Ubuntu k3s"
        vb.memory = "8192"
        vb.cpus = "1"
      
      args = []
      config.vm.provision "k3s shell script", type: "shell",
          path: "scripts/k3s.sh",
          args: args
          
      args = []
      config.vm.provision "helm shell script", type: "shell",
          path: "scripts/helm.sh",
          args: args
          
      args = []
      config.vm.provision "dashboard shell script", type: "shell",
          path: "scripts/dashboard.sh",
          args: args
          
    end
    
  end

end

Here, you can see I added some ports needed for the Quarkus guided code examples, later on.

From the subdirectory named env on my Windows laptop, I opened a Windows Command Prompt (cmd) and typed: vagrant up

This command creates and configures guest machines according to your Vagrantfile.
_{[https://www.vagrantup.com/docs/cli/up.html]}

With the following output (only showing the part about K3s):

I used vagrant ssh to connect into the running VM. Next, I used the following command on the Linux Command Prompt:

docker --version

With the following output:

Docker version 19.03.12, build 48a66213fe

This gave me the version of Docker, but also showed me, I could use Docker as a non-root user (being user vagrant).

Next, I continued with the steps to get started with Quarkus.

Step 1 You need an IDE

I installed IntelliJ IDEA Community Edition 2020.2 on my Windows laptop.
_{[https://www.jetbrains.com/idea/download/#section=windows]}

Step 2a You need a JDK 8 or 11+ (any distribution)

On the “QUARKUS – GET STARTED” page, I clicked on the link “a JDK 8 or 11+” in step 2.
_{[https://adoptopenjdk.net/]}

Quarkus - Supersonic Subatomic Java, setting up a demo environment using Vagrant and Oracle VirtualBox lameriks 2020 08 3

From there I clicked on the link “Installation”.
_{[https://adoptopenjdk.net/installation.html]}

Quarkus - Supersonic Subatomic Java, setting up a demo environment using Vagrant and Oracle VirtualBox lameriks 2020 08 4

From here I could have downloaded the tar.gz file, suitable for my environment:

https://github.com/AdoptOpenJDK/openjdk11-binaries/releases/download/jdk-11.0.8%2B10/OpenJDK11U-jdk_x64_linux_hotspot_11.0.8_10.tar.gz

Quarkus - Supersonic Subatomic Java, setting up a demo environment using Vagrant and Oracle VirtualBox lameriks 2020 08 5

But on the “Installation” page, I navigated to the Installers, and more specific to part about the Linux DEB installer packages.

Quarkus - Supersonic Subatomic Java, setting up a demo environment using Vagrant and Oracle VirtualBox lameriks 2020 08 6

So, I used the following command on the Linux Command Prompt:

wget -qO - https://adoptopenjdk.jfrog.io/adoptopenjdk/api/gpg/key/public | sudo apt-key add -

With the following output:

Next, I used the following command on the Linux Command Prompt:

sudo add-apt-repository --yes https://adoptopenjdk.jfrog.io/adoptopenjdk/deb/

With the following output:

Hit:1 http://archive.ubuntu.com/ubuntu bionic InRelease
Hit:2 http://archive.ubuntu.com/ubuntu bionic-updates InRelease
Hit:3 http://archive.ubuntu.com/ubuntu bionic-backports InRelease
Get:4 https://adoptopenjdk.jfrog.io/adoptopenjdk/deb bionic InRelease [6155 B]
Get:5 https://adoptopenjdk.jfrog.io/adoptopenjdk/deb bionic/main amd64 Packages [11.3 kB]
Hit:6 https://download.docker.com/linux/ubuntu bionic InRelease
Hit:7 http://security.ubuntu.com/ubuntu bionic-security InRelease
Fetched 17.5 kB in 5s (3273 B/s)
Reading package lists… Done

Next, I used the following command on the Linux Command Prompt:

sudo apt-get update

With the following output:

Hit:1 http://security.ubuntu.com/ubuntu bionic-security InRelease
Hit:2 https://download.docker.com/linux/ubuntu bionic InRelease
Hit:3 http://archive.ubuntu.com/ubuntu bionic InRelease
Hit:4 http://archive.ubuntu.com/ubuntu bionic-updates InRelease
Hit:5 http://archive.ubuntu.com/ubuntu bionic-backports InRelease
Hit:6 https://adoptopenjdk.jfrog.io/adoptopenjdk/deb bionic InRelease
Reading package lists… Done

Next, I used the following command on the Linux Command Prompt:

sudo apt-get install -y adoptopenjdk-11-hotspot

With the following output:

From this output I could see that for the JAVA_HOME environment variable, I will be using later on in this article, I had to use the path: /usr/lib/jvm/adoptopenjdk-11-hotspot-amd64

Step 2b Optionally get GraalVM 20.1.0 for native compilation

On the “QUARKUS – GET STARTED” page, I clicked on the link “GraalVM” in step 2.
_{[https://www.graalvm.org/]}

Quarkus - Supersonic Subatomic Java, setting up a demo environment using Vagrant and Oracle VirtualBox lameriks 2020 08 7

From there I clicked on the links “GET STARTED”, followed by “Install GraalVM” and “Linux”.
_{[https://www.graalvm.org/docs/getting-started/linux#installation-on-linux-platforms]}

Quarkus - Supersonic Subatomic Java, setting up a demo environment using Vagrant and Oracle VirtualBox lameriks 2020 08 8

I wanted to use the java11 variant. As you can see, the graalvm-ce-java11-linux-aarch64-20.1.0, is currently under development and is provided for evaluation and testing use. This was fine by me.

On the “Linux” page, in part “Installation on Linux Platform”, I clicked on the link “GraalVM Releases repository on GitHub”.
_{[https://github.com/graalvm/graalvm-ce-builds/releases]}

Then, I clicked on the link “GraalVM Community Edition 20.1.0”.
_{[https://github.com/graalvm/graalvm-ce-builds/releases/tag/vm-20.1.0]}

Quarkus - Supersonic Subatomic Java, setting up a demo environment using Vagrant and Oracle VirtualBox lameriks 2020 08 9

To download the tar.gz file, I used the following command on the Linux Command Prompt:

cd /tmp
wget https://github.com/graalvm/graalvm-ce-builds/releases/download/vm-20.1.0/graalvm-ce-java11-linux-amd64-20.1.0.tar.gz

With the following output:

–2020-08-16 15:44:28– https://github.com/graalvm/graalvm-ce-builds/releases/download/vm-20.1.0/graalvm-ce-java11-linux-amd64-20.1.0.tar.gz
Resolving github.com (github.com)… 140.82.118.3
Connecting to github.com (github.com)|140.82.118.3|:443… connected.
HTTP request sent, awaiting response… 302 Found
Location: https://github-production-release-asset-2e65be.s3.amazonaws.com/222889977/7d7c1380-99e7-11ea-8b4c-6129a7f24477?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20200816%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20200816T154429Z&X-Amz-Expires=300&X-Amz-Signature=616197d68308f4c0f7da55e88451e1ce3e381613d20c328c161f7995863edd0f&X-Amz-SignedHeaders=host&actor_id=0&repo_id=222889977&response-content-disposition=attachment%3B%20filename%3Dgraalvm-ce-java11-linux-amd64-20.1.0.tar.gz&response-content-type=application%2Foctet-stream [following]
–2020-08-16 15:44:36– https://github-production-release-asset-2e65be.s3.amazonaws.com/222889977/7d7c1380-99e7-11ea-8b4c-6129a7f24477?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20200816%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20200816T154429Z&X-Amz-Expires=300&X-Amz-Signature=616197d68308f4c0f7da55e88451e1ce3e381613d20c328c161f7995863edd0f&X-Amz-SignedHeaders=host&actor_id=0&repo_id=222889977&response-content-disposition=attachment%3B%20filename%3Dgraalvm-ce-java11-linux-amd64-20.1.0.tar.gz&response-content-type=application%2Foctet-stream
Resolving github-production-release-asset-2e65be.s3.amazonaws.com (github-production-release-asset-2e65be.s3.amazonaws.com)… 52.216.111.19
Connecting to github-production-release-asset-2e65be.s3.amazonaws.com (github-production-release-asset-2e65be.s3.amazonaws.com)|52.216.111.19|:443… connected.
HTTP request sent, awaiting response… 200 OK
Length: 442680579 (422M) [application/octet-stream]
Saving to: ‘graalvm-ce-java11-linux-amd64-20.1.0.tar.gz’

graalvm-ce-java11-linux-amd64-20.1.0.tar.g 100%[=======================================================================================>] 422.17M 4.25MB/s in 2m 48s

2020-08-16 15:47:25 (2.51 MB/s) – ‘graalvm-ce-java11-linux-amd64-20.1.0.tar.gz’ saved [442680579/442680579]

To unzip the archive in the /opt directory, I used the following command on the Linux Command Prompt:

sudo tar -xvf graalvm-ce-java11-linux-amd64-20.1.0.tar.gz -C /opt

With the following output:

From this output I could see that in order to prepend the GraalVM bin directory to the PATH environment variable, later on in this article, I had to use the path: /opt/graalvm-ce-java11-20.1.0/bin

Next, I used the following command on the Linux Command Prompt:

cd /opt
ls -latr

With the following output:

total 20
drwxr-xr-x  9 root root 4096 Aug 15 17:56 VBoxGuestAdditions-6.0.20
drwx–x–x  4 root root 4096 Aug 15 17:58 containerd
drwxr-xr-x 24 root root 4096 Aug 16 08:22 ..
drwxr-xr-x  5 root root 4096 Aug 16 17:39 .
drwxr-xr-x 10 root root 4096 Aug 16 17:39 graalvm-ce-java11-20.1.0

Remark:
You can also specify GraalVM as the JRE or JDK installation in your Java IDE.
_{[https://www.graalvm.org/docs/getting-started/linux#installation-on-linux-platforms]}

On the “Linux” page, I also had a look at part “Install Additional Components”.
_{[https://www.graalvm.org/docs/getting-started/linux#install-additional-components]}

Quarkus - Supersonic Subatomic Java, setting up a demo environment using Vagrant and Oracle VirtualBox lameriks 2020 08 10

I knew from reading through some of the guided code examples I wanted to do, I needed to install the native-image tool using gu install.
_{[https://quarkus.io/guides/building-native-image]}

Quarkus - Supersonic Subatomic Java, setting up a demo environment using Vagrant and Oracle VirtualBox lameriks 2020 08 11

On the “QUARKUS – BUILDING A NATIVE EXECUTABLE” page, I clicked on the link “configured appropriately”.
_{[https://quarkus.io/guides/building-native-image#configuring-graalvm]}

Quarkus - Supersonic Subatomic Java, setting up a demo environment using Vagrant and Oracle VirtualBox lameriks 2020 08 12

From this and the earlier output I could see that for the GRAALVM_HOME environment variable, I will be using later on in this article, I had to use the path: /opt/graalvm-ce-java11-20.1.0

To install the native-image tool, I used the following command on the Linux Command Prompt:

sudo ./opt/graalvm-ce-java11-20.1.0/bin/gu install native-image

With the following output:

sudo: ./opt/graalvm-ce-java11-20.1.0/bin/gu: command not found

Then I investigated the problem.

Next, I used the following command on the Linux Command Prompt:

cd /opt/graalvm-ce-java11-20.1.0/bin
ls -latr

With the following output:

Next, I used the following command on the Linux Command Prompt:

cd /opt/graalvm-ce-java11-20.1.0/lib/installer/bin
sudo ./gu install native-image

With the following output:

Downloading: Component catalog from www.graalvm.org
Processing Component: Native Image
Downloading: Component native-image: Native Image from github.com
Installing new component: Native Image (org.graalvm.native-image, version 20.1.0)

Step 3 You need Apache Maven 3.6.2+ or Gradle

On the “QUARKUS – GET STARTED” page, I clicked on the link “Apache Maven 3.6.2+” in step 3.
_{[https://maven.apache.org/]}

Quarkus - Supersonic Subatomic Java, setting up a demo environment using Vagrant and Oracle VirtualBox lameriks 2020 08 13

From there I clicked on the link “Download”.

Quarkus - Supersonic Subatomic Java, setting up a demo environment using Vagrant and Oracle VirtualBox lameriks 2020 08 14

To download the tar.gz file, I used the following command on the Linux Command Prompt:

cd /tmp
wget http://apache.cs.uu.nl/maven/maven-3/3.6.3/binaries/apache-maven-3.6.3-bin.tar.gz

With the following output:

–2020-08-17 06:47:58– http://apache.cs.uu.nl/maven/maven-3/3.6.3/binaries/apache-maven-3.6.3-bin.tar.gz
Resolving apache.cs.uu.nl (apache.cs.uu.nl)… 131.211.31.189
Connecting to apache.cs.uu.nl (apache.cs.uu.nl)|131.211.31.189|:80… connected.
HTTP request sent, awaiting response… 200 OK
Length: 9506321 (9.1M) [application/x-gzip]
Saving to: ‘apache-maven-3.6.3-bin.tar.gz’

apache-maven-3.6.3-bin.tar.gz 100%[=======================================================================================>] 9.07M 1.50MB/s in 7.3s

2020-08-17 06:48:06 (1.25 MB/s) – ‘apache-maven-3.6.3-bin.tar.gz’ saved [9506321/9506321]

On the “Welcome to Apache Maven” page, I clicked on the link “Install”.
_{[ https://maven.apache.org/install.html]}

Quarkus - Supersonic Subatomic Java, setting up a demo environment using Vagrant and Oracle VirtualBox lameriks 2020 08 15

To unzip the archive in the /opt directory, I used the following command on the Linux Command Prompt:

sudo tar xzvf apache-maven-3.6.3-bin.tar.gz -C /opt

With the following output:

In order to prepend the Maven bin directory to the PATH environment variable, later on in this article, I had to use the path: /opt/apache-maven-3.6.3/bin

Next, I used the following command on the Linux Command Prompt:

cd /opt
ls -latr

With the following output:

total 24
drwxr-xr-x  9 root root 4096 Aug 15 17:56 VBoxGuestAdditions-6.0.20
drwx–x–x  4 root root 4096 Aug 15 17:58 containerd
drwxr-xr-x 24 root root 4096 Aug 16 08:22 ..
drwxr-xr-x 10 root root 4096 Aug 16 17:39 graalvm-ce-java11-20.1.0
drwxr-xr-x  6 root root 4096 Aug 17 06:49 .
drwxr-xr-x  6 root root 4096 Aug 17 06:49 apache-maven-3.6.3

Step 4 Start Coding with Quarkus 1.7.0.Final

On the “QUARKUS – GET STARTED” page, I clicked on the link “Start Coding” in step 4.
_{[https://www.graalvm.org/]}

Quarkus - Supersonic Subatomic Java, setting up a demo environment using Vagrant and Oracle VirtualBox lameriks 2020 08 16

So apparently the “get started” steps were al done and I could now start coding with Quarkus.

You can read more about the code guides I tried out in my next article.

But, I still had to set some environment variables in order for my demo environment to work properly.

Permanently setting environment variables for all users

A suitable file for environment variable settings that affect the system as a whole (rather than just a particular user) is /etc/environment. An alternative is to create a file for the purpose in the /etc/profile.d directory.

Files with the .sh extension in the /etc/profile.d directory get executed whenever a bash login shell is entered (e.g. when logging in from the console or over ssh), as well as by the DisplayManager when the desktop session loads.
_{[https://help.ubuntu.com/community/EnvironmentVariables]}

In order to check the content of the /etc/environment file, I used the following command on the Linux Command Prompt:

cat /etc/environment

With the following output:

PATH=”/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games”

In order to check the content of the /etc/profile.d directory, I used the following command on the Linux Command Prompt:

cd /etc/profile.d
ls -latr

With the following output:

total 36
-rw-r–r–  1 root root 1003 Dec 29  2015 cedilla-portuguese.sh
-rw-r–r–  1 root root 1557 Dec  4  2017 Z97-byobu.sh
-rw-r–r–  1 root root  664 Apr  2  2018 bash_completion.sh
-rw-r–r–  1 root root   96 Sep 27  2019 01-locale-fix.sh
-rwxr-xr-x  1 root root  873 Jun  3 02:08 Z99-cloudinit-warnings.sh
-rwxr-xr-x  1 root root 3417 Jun  3 02:08 Z99-cloud-locale-test.sh
-rw-r–r–  1 root root  825 Jul 10 14:00 apps-bin-path.sh
drwxr-xr-x  2 root root 4096 Aug 12 15:55 .
drwxr-xr-x 95 root root 4096 Aug 17 14:26 ..

In order to set some environment variables permanently, I used the following command on the Linux Command Prompt in order to create and edit the file myenvvars.sh:

sudo vim myenvvars.sh

And I changed the content to:

export JAVA_HOME=/usr/lib/jvm/adoptopenjdk-11-hotspot-amd64
export PATH=$JAVA_HOME/bin:$PATH
export GRAALVM_HOME=/opt/graalvm-ce-java11-20.1.0
export PATH=${GRAALVM_HOME}/bin:$PATH
export PATH=/opt/apache-maven-3.6.3/bin:$PATH

Next, I used vagrant ssh to connect into the running VM and checked if the environment variables were set correctly.

In order to check the Java version, I used the following command on the Linux Command Prompt:

java --version

With the following output:

openjdk 11.0.7 2020-04-14
OpenJDK Runtime Environment GraalVM CE 20.1.0 (build 11.0.7+10-jvmci-20.1-b02)
OpenJDK 64-Bit Server VM GraalVM CE 20.1.0 (build 11.0.7+10-jvmci-20.1-b02, mixed mode, sharing)

In order to check the Maven version, I used the following command on the Linux Command Prompt:

mvn -v

With the following output:

Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
Maven home: /opt/apache-maven-3.6.3
Java version: 11.0.8, vendor: AdoptOpenJDK, runtime: /usr/lib/jvm/adoptopenjdk-11-hotspot-amd64
Default locale: en, platform encoding: UTF-8
OS name: “linux”, version: “4.15.0-112-generic”, arch: “amd64”, family: “unix”

With these final checks I conclude this article. I shared with you the steps I took to set up a demo environment, so I could get started with Quarkus. In a next article, you can read more about the code guides I tried out.

Quarkus – Supersonic Subatomic Java, setting up a demo environment using Vagrant and Oracle VirtualBox

Quarkus

Quarkus at Devoxx Belgium 2019

GraalVM

Quarkus – get started

Step 1 You need an IDE

Step 2a You need a JDK 8 or 11+ (any distribution)

Step 2b Optionally get GraalVM 20.1.0 for native compilation

Step 3 You need Apache Maven 3.6.2+ or Gradle

Step 4 Start Coding with Quarkus 1.7.0.Final

Like this:

About The Author

Marc Lameriks

One Response

Quarkus

Quarkus at Devoxx Belgium 2019

GraalVM

Quarkus – get started

Step 1 You need an IDE

Step 2a You need a JDK 8 or 11+ (any distribution)

Step 2b Optionally get GraalVM 20.1.0 for native compilation

Step 3 You need Apache Maven 3.6.2+ or Gradle

Step 4 Start Coding with Quarkus 1.7.0.Final

Share this:

Like this:

Related Posts

About The Author

Marc Lameriks

One Response