Skip to content

Commit c3a8051

Browse files
author
vibhuti sodhi
committed
all points added & verfied by QEs
1 parent b9ef9a5 commit c3a8051

File tree

3 files changed

+16
-28
lines changed

3 files changed

+16
-28
lines changed

docs/release-notes/master.adoc

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -24,8 +24,6 @@ include::topics/ref_known-issues-7-1-1.adoc[leveloffset=+2]
2424

2525
include::topics/ref_resolved-issues-7-1-1.adoc[leveloffset=+2]
2626

27-
:!release-notes:
28-
2927
[id="mta-7-1-0"]
3028
== {ProductShortName} 7.1.0
3129

docs/topics/ref_known-issues-7-1-1.adoc

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,6 +8,10 @@
88

99
This section provides highlighted known issues in {ProductFullName} version 7.1.1.
1010

11-
.<to-add>
11+
.Unable to perform bulk analysis on Windows systems
1212

13-
<to-add>. (link:https://issues.redhat.com/browse/MTA-xxxx[MTA-xxxx])
13+
In {ProductShortName} CLI 7.1.0, bulk analysis on Windows systems cannot be performed. Currently, there is no workaround available. (link:https://issues.redhat.com/browse/MTA-3624[MTA-3624])
14+
15+
.Binary analysis fails with incorrect Maven credentials
16+
17+
Binary analysis fails with a generic error when incorrect Maven credentials are used. This occurs because the analyzer is unable to report detailed error messages. (link:https://issues.redhat.com/browse/MTA-3714[MTA-3714])

docs/topics/ref_resolved-issues-7-1-1.adoc

Lines changed: 10 additions & 24 deletions
Original file line numberDiff line numberDiff line change
@@ -21,42 +21,28 @@ ERRO[0143] container run error
2121
ERRO[0143] failed to generate static report
2222
----
2323

24-
With this update, the issue has been resolved, and the bulk analysis completes without errors and generates a proper analysis report.
25-
26-
:FeatureName: <<TO-ADD>>
27-
28-
//link:https:https://issues.redhat.com/browse/MTA-3663[MTA-3663]
24+
With this update, the issue has been resolved, and the bulk analysis completes without errors and generates a proper analysis report. (link:https:https://issues.redhat.com/browse/MTA-3663[MTA-3663])
2925

3026
.Enabling Preemption now works as expected if authentication is enabled
3127

32-
Previously, *Preemption* could not be enabled for tasks in the *Task Manager* page and the Task Manager drawer if {ProductFullName} authentication was enabled. With this update, the issue has been resolved, and you can now enable *Preemption* if {ProductFullName} authentication is enabled.
33-
34-
:FeatureName: <<TO-ADD>>
35-
36-
//link:https:https://issues.redhat.com/browse/MTA-3195[MTA-3195]
28+
Previously, *Preemption* could not be enabled for tasks in the *Task Manager* page and the Task Manager drawer if {ProductFullName} authentication was enabled. With this update, the issue has been resolved, and you can now enable *Preemption* if {ProductFullName} authentication is enabled.(link:https:https://issues.redhat.com/browse/MTA-3195[MTA-3195])
3729

3830
.The drop-down application menu no longer contains duplicate options
3931

40-
Previously, when selecting a target for application analysis, the drop-down menu contained duplicate application target options. With this update, the issue has been resolved, and no duplicates are listed when selecting the application analysis target.
41-
42-
:FeatureName: <<TO-ADD>>
43-
44-
//link:https:https://issues.redhat.com/browse/MTA-2795[MTA-2795]
45-
32+
Previously, when selecting a target for application analysis, the drop-down menu contained duplicate application target options. With this update, the issue has been resolved, and no duplicates are listed when selecting the application analysis target. (link:https:https://issues.redhat.com/browse/MTA-2795[MTA-2795])
4633

4734
.The Reports page now displays separate charts for unassessed applications and applications with the Unknown risk
4835

49-
Previously, the {ProductFullName} user interface (UI) did not distinguish between unassessed applications and applications that have been assessed to have the `Unknown` risk. Consequently, the *Reports* page displayed a single chart for such applications. With this update, the issue has been resolved, and the *Reports* page now displays separate charts for unassessed applications and applications with the *Unknown* risk.
50-
51-
:FeatureName: <<TO-ADD>>
36+
Previously, the {ProductFullName} user interface (UI) did not distinguish between unassessed applications and applications that have been assessed to have the `Unknown` risk. Consequently, the *Reports* page displayed a single chart for such applications. With this update, the issue has been resolved, and the *Reports* page now displays separate charts for unassessed applications and applications with the *Unknown* risk. (link:https:https://issues.redhat.com/browse/MTA-2678[MTA-2678])
5237

53-
//link:https:https://issues.redhat.com/browse/MTA-2678[MTA-2678]
38+
.Analyzing public applications no longer fails
5439

40+
Previously, when you ran an analysis for public applications, which do not require credentials, by using custom rules, the analysis would fail if no targets and maven or source credentials were provided. With this update, the issue has been resolved, and the analysis no longer fails for public applications. (link:https:https://issues.redhat.com/browse/MTA-3163[MTA-3163])
5541

56-
.Analyzing public applications no longer fails
42+
.Successful application analysis despite dependency analysis failures
5743

58-
Previously, when you ran an analysis for public applications, which do not require credentials, by using custom rules, the analysis would fail if no targets and maven or source credentials were provided. With this update, the issue has been resolved, and the analysis no longer fails for public applications.
44+
Previously, the application analysis failed due to a dependency analysis issue, even when the source code analysis was successful, resulting in no static report being generated. This issue has been resolved now in the {ProductShortName} CLI. (link:https:https://issues.redhat.com/browse/MTA-3700[MTA-3700])
5945

60-
:FeatureName: <<TO-ADD>>
46+
.Improved container naming
6147

62-
//link:https:https://issues.redhat.com/browse/MTA-3163[MTA-3163]
48+
Previously, container names contained random letters, making their identification difficult. The issue has been resolved in {ProductShortName} 7.1.1, where container names now have readable prefixes for easier identification. (link:https:https://issues.redhat.com/browse/MTA-3133[MTA-3133])

0 commit comments

Comments
 (0)