Merge branch 'main' into mta-5094-rn-7.3.0-known-issue

Author: Pkylas007

docs/release-notes/master.adoc

@@ -18,6 +18,11 @@ include::topics/making-open-source-more-inclusive.adoc[]
 
 {ProductFullName} {DocInfoProductNumber} accelerates large-scale application modernization efforts across hybrid cloud environments on {ocp-first}. This solution provides insight throughout the adoption process, at both the portfolio and application levels: inventory, assess, analyze, and manage applications for faster migration to {ocp-short} through the user interface (UI) and command-line interface (CLI).
 
+[id="mta-7-3-0"]
+== {ProductShortName} 7.3.0
+
+include::topics/ref_known-issues-7-3-0.adoc[leveloffset=+2]
+
 [id="mta-7-2-2"]
 == {ProductShortName} 7.2.2
 

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

@@ -11,3 +11,6 @@ When you analyze Java applications, {ProductShortName} rules can trigger a false
 
 .Source code and dependency analysis of Java applications generate varying effort
 When you run multiple `source code + dependency` repeated analysis of Java applications for the `OpenJDK 17` target, {ProductShortName} generates varying effort. Currently, there is no workaround for this issue. link:https://issues.redhat.com/browse/MTA-4943[(MTA-4943)]
+
+.Application credential update does not trigger a new discovery task
+When you update the source or Maven credential for an application, a new discovery task is not triggered in the {ProductShortName} {WebName}. link:https://issues.redhat.com/browse/MTA-5121[(MTA-5121)]

docs/topics/ref_known-issues-7-3-0.adoc

@@ -8,3 +8,14 @@ This section provides highlighted known issues in {ProductFullName} version 7.3.
 
 .Non-Java applications are analyzed in containerless mode in the {ProductShortName} CLI
 When you analyze non-Java applications, {ProductShortName} initiates the analysis in containerless mode. Workaround: set the `--run-local=false` flag to analyze non-Java applications. link:https://issues.redhat.com/browse/MTA-5068[MTA-5068]
+=======
+.`.NET` Framework application analysis fails in the {ProductShortName} {CLIName} 
+When you analyze `.NET` Framework applications in Windows containers using the {ProductShortName} {CLIName}, the analysis fails for the following environment variables: 
+
+* `DOTNET_PROVIDER_IMG`: `quay.io/konveyor/dotnet-external-provider:release-0.7`
+* `RUNNER_IMG`: `quay.io/konveyor/kantra:latest`
+* `PODMAN_BIN`: `C:\Program Files\Docker\Docker\resources\bin\docker.exe`
+
+Workaround: Use the following version of the Dotnet provider image:
+`set DOTNET_PROVIDER_IMG=quay.io/konveyor/dotnet-external-provider:v0.5.0` 
+link:https://issues.redhat.com/browse/MTA-5203[(MTA-5203)]

docs/topics/ref_resolved-issues-7-3-0.adoc

@@ -0,0 +1,14 @@
+// Module included in the following assemblies:
+//
+//docs/release_notes-7.2.0/master.adoc
+
+:_template-generated: 2024-12-04
+:_mod-docs-content-type: REFERENCE
+
+[id="resolved-issues-7-3-0_{context}"]
+= Resolved issues
+
+This section provides highlighted issues that have been resolved in {ProductFullName} 7.3.0.
+
+.MTA CLI now excludes the `target` folder when analyzing compiled Java Maven projects
+Previously, for compiled Java Maven projects, the {ProductShortName} CLI included incidents by analyzing the `target` folder. This generated different reports for Java Maven projects before and after running the `mvn-clean-package` command. This issue has been resolved in {ProductShortName} 7.3.0. link:https://issues.redhat.com/browse/MTA-5078[(MTA-5078)]