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
@@ -359,6 +359,19 @@ Then, for each file or class affected by the incident, you can jump into the sou
359
359
360
360
## Release notes
361
361
362
+
### 7.6.0.1
363
+
364
+
This release contains the following fixes and enhancements.
365
+
366
+
-`--analyze-known-libraries` flag: Now works on Windows.
367
+
- Directory cleanup: Extra directories created during analysis on Windows are now automatically cleaned up.
368
+
-`--json-output` flag: Now operational.
369
+
- Rules parsing error: The error `unable to parse all the rules for ruleset` has been resolved.
370
+
- Insights tab descriptions: Missing rule descriptions have been added.
371
+
- Internet connection dependency: Analysis no longer fails without an internet connection.
372
+
-`--context-lines` flag: Now behaves as expected when set to 0.
373
+
- Removed Python requirement to run the tool.
374
+
362
375
### 7.6.0.0
363
376
364
377
This release is based on a different set of components of the Konveyor project.
@@ -411,27 +424,38 @@ GA (Generally Available) release of Azure Migrate application and code assessmen
411
424
412
425
## Known Issues
413
426
427
+
### 7.6.0.1
428
+
429
+
- The flag `--overrideProviderSettings` isn't supported.
430
+
- Rules issues:
431
+
-`azure-system-config-01000`, `http-session-01000`, `java-removals-00150` rules aren't being triggered.
432
+
-`FileSystem - Java IO` rule isn't being triggered.
433
+
- 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.
434
+
- 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.
435
+
- <kbd>Ctrl</kbd>+<kbd>C</kbd> fails to stop ongoing analysis. To work around, manually terminate the process by explicitly killing the process.
436
+
- In binary analysis reports, the code snippet title shows an incorrect or non-existent file path.
437
+
414
438
### 7.6.0.0
415
439
416
-
1. The flag `--analyze-known-libraries` isn't working on Windows.
417
-
1. On Windows, the following extra folders are generated during the analysis process but aren't automatically removed after completion. You might want to remove these extra folders after the analysis finishes.
440
+
- The flag `--analyze-known-libraries` isn't working on Windows.
441
+
- On Windows, the following extra folders are generated during the analysis process but aren't automatically removed after completion. You might want to remove these extra folders after the analysis finishes.
418
442
-**.metadata**
419
443
-**org.eclipse.osgi**
420
444
-**org.eclipse.equinox.app**
421
445
-**org.eclipse.core.runtime**
422
446
-**org.eclipse.equinox.launcher**
423
-
1. The flag `--overrideProviderSettings` isn't supported.
424
-
1. The flag `--json-output` isn't supported. In a future release, it generates JSON outputs for the **output.yaml** and **dependency.yaml** files.
425
-
1. Rules issues:
426
-
-**azure-system-config-01000**, **http-session-01000**, **java-removals-00150** rules aren't being triggered.
427
-
-**FileSystem - Java IO** rule isn't being triggered
428
-
-_"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.
429
-
1. 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.
430
-
1. 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.
431
-
1. 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.
432
-
1. This release requires an active internet connection for dependency analysis.
433
-
1. <kbd>Ctrl</kbd>+<kbd>C</kbd> fails to stop ongoing analysis. To work around, manually terminate the process by explicitly killing the process.
434
-
1. When the flag `--context-lines` is set to a number 0, it doesn't work as expected. This flag allows the user to limit how much of the source code should appear on the report. Setting to a value 0 might not work as expected.
447
+
- The flag `--overrideProviderSettings` isn't supported.
448
+
- The flag `--json-output` isn't supported. In a future release, it generates JSON outputs for the **output.yaml** and **dependency.yaml** files.
449
+
- Rules issues:
450
+
-`azure-system-config-01000`, `http-session-01000`, `java-removals-00150` rules aren't being triggered.
451
+
-`FileSystem - Java IO` rule isn't being triggered.
452
+
-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.
453
+
- 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.
454
+
- 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.
455
+
- 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.
456
+
- This release requires an active internet connection for dependency analysis.
457
+
- <kbd>Ctrl</kbd>+<kbd>C</kbd> fails to stop ongoing analysis. To work around, manually terminate the process by explicitly killing the process.
458
+
- When the flag `--context-lines` is set to a number 0, it doesn't work as expected. This flag allows the user to limit how much of the source code should appear on the report. Setting to a value 0 might not work as expected.
0 commit comments