Skip to content

Commit 9743869

Browse files
author
Prabha Kylasamiyer Sundara Rajan
committed
Set 1 fixed issues
1 parent 0966ae5 commit 9743869

File tree

1 file changed

+15
-0
lines changed

1 file changed

+15
-0
lines changed

docs/topics/ref_fixed-issues-7-3-2.adoc

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -8,3 +8,18 @@
88

99
This section provides the following bug fixes and resolved issues and other problems that have a significant impact on the {ProductFullName} 7.3.2.
1010

11+
.{ProductShortName} now generates consistent results after analyzing large .EAR binary files
12+
13+
Previously, when analyzing binary applications, MTA relied on the Maven search index to determine whether dependencies are internal to the application or whether the application was installed as an open-source dependency. Depending on the availability of the Maven search index, it was assumed that an open-source dependency was internal to the application and includes the dependency in the analysis results. In this case, analysis returned more incidents and greater effort to address issues found in dependencies, even if the user did not expect to see those results. This issue has been resolved in {ProductShortName} 7.3.2. link:https://issues.redhat.com/browse/MTA-5588[(MTA-5588)]
14+
15+
.{ProductShortName} does not generate false positives when analyzing Java applications
16+
17+
Previously, {ProductShortName} generated a false positive after analyzing a Java application with targets containerization and Jakarta EE9 by triggering a rule that is not relevant. This issue has been resolved in {ProductShortName} 7.3.2. link:https://issues.redhat.com/browse/MTA-4025[(MTA-4025)]
18+
19+
.{ProductShortName} {WebName} analysis does not skip issues for Java applications
20+
21+
Previously in 7.3.0, when you performed source+dependency analysis of Java applications, {ProductShortName} {WebName} missed generating issues when compared with the results generated in earlier versions. This issue has been resolved in {ProductShortName} 7.3.2. link:https://issues.redhat.com/browse/MTA-4824[MTA-4284]
22+
23+
.{ProductShortName} {CLIName} generates a process error in log after Java binary analysis using Microsoft Windows
24+
25+
Previously, when you analyzed Java binaries using Microsoft Windows, {ProductShortName} {CLIName} generated a process error when deleting files in the `exploded` directory after moving the decompiled files to the Java project path. The process error did not affect the analysis results. This issue has been resolved in {ProductShortName} 7.3.2. link:https://issues.redhat.com/browse/MTA-5355[(MTA-5355)]

0 commit comments

Comments
 (0)