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
Copy file name to clipboardExpand all lines: articles/migrate/appcat/java-preview.md
+5-6Lines changed: 5 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@ ms.date: 01/08/2025
10
10
#customer intent: As a developer, I want to assess my Java application so that I can understand its readiness for migration to Azure.
11
11
---
12
12
13
-
# Azure Migrate application and code assessment for Java
13
+
# Azure Migrate application and code assessment for Java version 7 (Preview)
14
14
15
15
> [!Note]
16
16
> This documentation is for the next generation of _Azure Migrate application and code assessment for Java_**version 7.x**. This version is in **preview**.
@@ -43,13 +43,12 @@ The tool contains rules for helping you replatform your applications so you can
43
43
44
44
The rules used by Azure Migrate application and code assessment are grouped based on a *target*. A target is where or how the application runs, and general needs and expectations. When assessing an application, you can choose multiple targets. The following table describes the available targets:
| Azure App Service | Best practices for deploying an app to Azure App Service. |`azure-appservice`|
49
49
| Azure Kubernetes Service | Best practices for deploying an app to Azure Kubernetes Service. |`azure-aks`|
50
50
| Azure Container Apps | Best practices for deploying an app to Azure Container Apps. |`azure-container-apps`|
51
51
| Cloud Readiness | General best practices for making an application Cloud (Azure) ready. |`cloud-readiness`|
52
-
| Discovery | Identifies technology usage such as libraries and frameworks. |`discovery`|
53
52
| Linux | General best practices for making an application Linux ready. |`linux`|
54
53
| OpenJDK 11 | General best practices for running a Java 8 application with Java 11. |`openjdk11`|
55
54
| OpenJDK 17 | General best practices for running a Java 11 application with Java 17. |`openjdk17`|
@@ -104,7 +103,7 @@ For the JDK requirement, we recommend you use the [Microsoft Build of OpenJDK](/
104
103
### Prerequisites
105
104
106
105
-[Download](/java/openjdk/download#openjdk-17) and [install Microsoft Build of OpenJDK 17](/java/openjdk/install). Ensure that the **JAVA_HOME** environment variable is set.
107
-
-[Download Apache Maven](https://maven.apache.org/download.cgi) and [install locally](https://maven.apache.org/install.html).
106
+
-[Download Apache Maven](https://maven.apache.org/download.cgi) and [install locally](https://maven.apache.org/install.html). Ensure that the Maven binary (`mvn`) is reachable through `PATH` environment variable.
108
107
-[Download and install Python 3](https://www.python.org/downloads/).
109
108
110
109
### Installation
@@ -150,12 +149,12 @@ On Windows, this is `%USERPROFILE%/.appcat` and on Linux/Mac, this is `$HOME/.ap
150
149
151
150
Add the `.appcat` folder to your PATH environment variable so you can run the tool from any folder in the terminal.
0 commit comments