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
@@ -122,40 +122,10 @@ Extract the binary from the downloaded file. You should see the following folder
122
122
123
123
### Running the tool
124
124
125
-
#### Option 1: Add the appcat binary path to your $PATH
126
-
127
-
Move the contents of the folder to the **.appcat** folder in the user's home directory - **$HOME/.appcat** on Linux/Mac and **%USERPROFILE%/.appcat** on Windows.
128
-
129
-
Add the **.appcat** folder to your `PATH` environment variable so you can run the tool from any folder in the terminal.
To run the `appcat` from any location in your terminal, extract the archive to your desired location, for example, `~/.appcat` on Linux/Mac or `%USERPROFILE%\.appcat` on Windows, then update the `PATH` environment variable to include the directory where you extracted the archive.
144
126
145
127
> [!NOTE]
146
-
> When the `appcat` binary is called from a different folder than where it's installed, it looks for its dependencies in the **.appcat** folder in the user's home directory.
147
-
148
-
#### Option 2: Run appcat from the downloaded folder
149
-
150
-
Change the directory to the extracted folder:
151
-
152
-
```bash
153
-
cd /azure-migrate-appcat-for-java-cli-<OS>-<architecture>-<release-version>-preview/
154
-
./appcat --help
155
-
```
156
-
157
-
> [!NOTE]
158
-
> The `appcat` binary first looks for its dependencies in the current directory. If the dependencies aren't found, it falls back to the configuration described in the [Option 1](#option-1-add-the-appcat-binary-path-to-your-path) section.
128
+
> When the `appcat` binary is called, it first looks for its dependencies in the executable folder specified in the `PATH` environment variable. If the dependencies aren't found, it falls back to the user's home directory - `~/.appcat` on Linux/Mac or `%USERPROFILE%\.appcat` on Windows.
159
129
160
130
## Usage
161
131
@@ -249,24 +219,46 @@ openjdk21
249
219
250
220
#### Analyzing Multiple Applications
251
221
252
-
AppCAT is designed to analyze a single application per command execution, but if you use the `--bulk` option, you can analyze multiple applications in a single execution. This option generates a single static report in the output directory that includes the results for all applications.
222
+
AppCAT supports multiple applications analysis in per command execution.
223
+
You can provide a comma-separated list of input paths for the `--input` flag to analyze multiple applications in a single command.
224
+
The output directory and static report will include the combined analysis results for all applications.
253
225
254
226
To analyze multiple applications, run the following command:
@@ -358,6 +350,12 @@ Then, for each file or class affected by the incident, you can jump into the sou
358
350
359
351
## Release notes
360
352
353
+
### 7.6.0.5
354
+
355
+
This release contains the following fixes and enhancements.
356
+
357
+
358
+
361
359
### 7.6.0.4
362
360
363
361
This release contains the following fixes and enhancements.
@@ -454,6 +452,13 @@ GA (Generally Available) release of Azure Migrate application and code assessmen
454
452
455
453
## Known Issues
456
454
455
+
### 7.6.0.5
456
+
457
+
- Rules issues:
458
+
- The `azure-system-config-01000` rules aren't being triggered.
459
+
- The `azure-password-01000` rule detects only one violation, even when multiple violations exist in the same file.
460
+
- An error in the 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.
0 commit comments