You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you intend to run the Java SE sections of this quickstart, the sample app requires Java 17. The steps in this section show you how to check if your Cloud Shell instance supports Java 17, and how to install it does not.
41
+
42
+
1. In the Azure Cloud Shell, enter `java -version`. If the output includes a version 17 or later, skip the rest of the steps in this section.
43
+
1. Enter these commands to download and extract the Microsoft build of OpenJDK.
1. Enter these commands to override the built-in Open JDK installed in Azure Cloud Shell.
50
+
51
+
> [!TIP]
52
+
> You must do this every time you open a new cloud shell, because the environment variables do not persist across cloud shell invocations. However, the files do persist.
53
+
54
+
```azurecli-interactive
55
+
cd jdk-17*
56
+
export JAVA_HOME=`pwd`
57
+
cd ..
58
+
export PATH=${JAVA_HOME}/bin:$PATH
59
+
java -version
60
+
```
61
+
62
+
You should see output stating the version of Java is 17 or greater. If not, troubleshoot and resolve the problem before continuing.
63
+
38
64
## 2 - Create a Java app
39
65
40
66
# [Java SE](#tab/javase)
@@ -57,7 +83,7 @@ mvn clean install
57
83
cd booty-duke-app-service
58
84
```
59
85
60
-
86
+
If you see a message about being in **detached HEAD** state, this message is safe to ignore. Because you will not be making any commits, detached HEAD state is appropriate.
61
87
62
88
# [Tomcat](#tab/tomcat)
63
89
@@ -93,6 +119,8 @@ cd petstore-ee7
93
119
mvn clean install
94
120
```
95
121
122
+
If you see a message about being in **detached HEAD** state, this message is safe to ignore. Because you will not be making any commits, detached HEAD state is appropriate.
0 commit comments