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
+10-10Lines changed: 10 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -332,25 +332,25 @@ The landing page of the report presents a summary view of all analyzed applicati
332
332
333
333
:::image type="content" source="media/java/appcat-7-report-summary.png" alt-text="Screenshot of the appcat summary report." lightbox="media/java/appcat-7-report-summary.png":::
334
334
335
-
The *Ask Copilot* button in the upper-right corner redirects you to the *GitHub Copilot App Modernization for Java* extension in Visual Studio Code, which provides an interactive experience for migrating Java applications - powered by AppCAT and GitHub Copilot's AI capabilities.
335
+
The *Ask Copilot* button in the upper-right corner redirects you to the *GitHub Copilot App Modernization for Java* extension in Visual Studio Code, which provides both app assessment and code remediation as its key capabilities for migrating Java applications to Azure - powered by AppCAT and GitHub Copilot's AI capabilities.
336
336
337
337
### Assessment report
338
338
339
-
The assessment report provides an overview of the transformation issues that need to be addressed to successfully migrate the application to Azure.
339
+
The assessment report provides a categorized issue list in aspects of Azure readiness, cloud native and Java modernization that need to be addressed to successfully migrate the application to Azure.
340
340
341
-
Each *Issue*, also referred to as an *Incident*, is categorized by severity (Mandatory, Optional, or Potential) and includes the number of impacted lines of code.
341
+
Each *Issue* is categorized by severity (Mandatory, Optional, or Potential) and includes the number of impacted lines of code.
342
342
343
343
The *Dependencies* and *Technologies* tabs display the libraries and technologies used within the application.
344
344
345
345
:::image type="content" source="media/java/appcat-7-report-assessment.png" alt-text="Screenshot of the AppCAT assessment report." lightbox="media/java/appcat-7-report-assessment.png":::
346
346
347
347
### Detailed information for a specific issue
348
348
349
-
For each incident, you can get more information (the issue detail, the content of the rule, and so on) just by selecting it. You also get the list of all the files affected by this incident.
349
+
For each issue, you can get more information (the issue detail, the content of the rule, and so on) just by selecting it. You also get the list of all the files affected by this issue.
350
350
351
351
:::image type="content" source="media/java/appcat-7-report-assessment-detail.png" alt-text="Screenshot of the AppCAT issue detail report." lightbox="media/java/appcat-7-report-assessment-detail.png":::
352
352
353
-
Then, for each file or class affected by the incident, you can jump into the source code to highlight the line of code that created the issue.
353
+
Then, for each file or class affected by the issue, you can jump into the source code to highlight the line of code that created the issue.
354
354
355
355
:::image type="content" source="media/java/appcat-7-report-assessment-code.png" alt-text="Screenshot of the AppCAT issue code report." lightbox="media/java/appcat-7-report-assessment-code.png":::
356
356
@@ -466,7 +466,7 @@ This release contains the following fixes and includes a set of new rules.
466
466
467
467
### 6.3.0.8
468
468
469
-
Previously, a set of targets were enabled by default, making it difficult for certain customers to assess large applications with too many incidents related to less critical issues. To reduce noise in reports, users must now specify multiple targets, with the parameter `--target`, when executing `appcat`, giving them the option to select only the targets that matter.
469
+
Previously, a set of targets were enabled by default, making it difficult for certain customers to assess large applications with too many issues related to less critical issues. To reduce noise in reports, users must now specify multiple targets, with the parameter `--target`, when executing `appcat`, giving them the option to select only the targets that matter.
470
470
471
471
### 6.3.0.7
472
472
@@ -501,7 +501,7 @@ GA (Generally Available) release of Azure Migrate application and code assessmen
501
501
- Rules issues:
502
502
-`azure-system-config-01000`, `http-session-01000` rules aren't being triggered.
503
503
-`FileSystem - Java IO` rule isn't being triggered.
504
-
- Analyzing WAR files on Windows produces the following error: `Failed to Move Decompiled File`. An error occurs when analyzing WAR files on Windows, which is responsible for a few redundant incidents created on Windows OS.
504
+
- Analyzing WAR files on Windows produces the following error: `Failed to Move Decompiled File`. An error occurs when analyzing WAR files on Windows, which is responsible for a few redundant issues created on Windows OS.
505
505
- Error in Watcher Error channel on Windows: `Windows system assumed buffer larger than it is, events have likely been missed`. This error message appears on the command line during long-running jobs on Windows.
506
506
- <kbd>Ctrl</kbd>+<kbd>C</kbd> fails to stop ongoing analysis. To work around, manually terminate the process by explicitly killing the process.
507
507
- In binary analysis reports, the code snippet title shows an incorrect or nonexistent file path.
@@ -512,7 +512,7 @@ GA (Generally Available) release of Azure Migrate application and code assessmen
512
512
- Rules issues:
513
513
-`azure-system-config-01000`, `http-session-01000` rules aren't being triggered.
514
514
-`FileSystem - Java IO` rule isn't being triggered.
515
-
- Analyzing WAR files on Windows produces the following error: `Failed to Move Decompiled File`. An error occurs when analyzing WAR files on Windows, which is responsible for a few redundant incidents created on Windows OS.
515
+
- Analyzing WAR files on Windows produces the following error: `Failed to Move Decompiled File`. An error occurs when analyzing WAR files on Windows, which is responsible for a few redundant issues created on Windows OS.
516
516
- Error in Watcher Error channel on Windows: `Windows system assumed buffer larger than it is, events have likely been missed`. This error message appears on the command line during long-running jobs on Windows.
517
517
- <kbd>Ctrl</kbd>+<kbd>C</kbd> fails to stop ongoing analysis. To work around, manually terminate the process by explicitly killing the process.
518
518
- In binary analysis reports, the code snippet title shows an incorrect or nonexistent file path.
@@ -523,7 +523,7 @@ GA (Generally Available) release of Azure Migrate application and code assessmen
523
523
- Rules issues:
524
524
-`azure-system-config-01000`, `http-session-01000`, `java-removals-00150` rules aren't being triggered.
525
525
-`FileSystem - Java IO` rule isn't being triggered.
526
-
- Analyzing WAR files on Windows produces the following error: `Failed to Move Decompiled File`. An error occurs when analyzing WAR files on Windows, which is responsible for a few redundant incidents created on Windows OS.
526
+
- Analyzing WAR files on Windows produces the following error: `Failed to Move Decompiled File`. An error occurs when analyzing WAR files on Windows, which is responsible for a few redundant issues created on Windows OS.
527
527
- Error in Watcher Error channel on Windows: `Windows system assumed buffer larger than it is, events have likely been missed`. This error message appears on the command line during long-running jobs on Windows.
528
528
- <kbd>Ctrl</kbd>+<kbd>C</kbd> fails to stop ongoing analysis. To work around, manually terminate the process by explicitly killing the process.
529
529
- In binary analysis reports, the code snippet title shows an incorrect or nonexistent file path.
@@ -543,7 +543,7 @@ GA (Generally Available) release of Azure Migrate application and code assessmen
543
543
-`azure-system-config-01000`, `http-session-01000`, `java-removals-00150` rules aren't being triggered.
544
544
-`FileSystem - Java IO` rule isn't being triggered.
545
545
- Error `unable to parse all the rules for ruleset` when running analysis. This error occurs during analysis when the tool fails to parse all rules in the ruleset.
546
-
- Analyzing WAR files on Windows produces the following error: `Failed to Move Decompiled File`. An error occurs when analyzing WAR files on Windows, which is responsible for a few redundant incidents created on Windows OS.
546
+
- Analyzing WAR files on Windows produces the following error: `Failed to Move Decompiled File`. An error occurs when analyzing WAR files on Windows, which is responsible for a few redundant issues created on Windows OS.
547
547
- Missing descriptions for some rules on the **Insights** tab. Some tag rules are lacking descriptions, leading to blank titles appearing on the **Insights** tab of the report.
548
548
- Error in **Watcher Error** channel on Windows: `Windows system assumed buffer larger than it is, events have likely been missed`. This error message appears on the command line during long-running jobs on Windows.
549
549
- This release requires an active internet connection for dependency analysis.
0 commit comments