Filename doesn't contain the actual class name in which the issue was found when analyzing dependencies

[rromannissen]

Environment

• Fedora 36
• minikube v1.31.2 (--driver=kvm2 --memory=10g --cpus=3)
• Konveyor 0.3 alpha-2 with additional images:
  • ui_image_fqin: quay.io/ibolton/tackle2-ui:demo
  • hub_image_fqin: quay.io/jortel/tackle2-hub:demo
  • analyzer_fqin: quay.io/jortel/tackle2-addon-analyzer:demo
• tackle-testapp application
• Analysis configuration:
  • Source + Dependencies
  • cloud-readiness, linux
  • Application and internal dependencies only
  • No custom rules
  • No additional advanced options

Description

When an issue is found in a dependency, the filename that gets displayed only contains the JAR file name, but it doesn't point to the actual file inside the JAR in which the issue has been found.

How to reproduce

• Analyze tackle-test app with the configuration available in the Environment section.
• Go to the issues view, Single application and filter by the tackle-testapp application.
• Select the Java Mail API issue.
• The list of affected files displays /root/.m2/repository/ch/qos/logback/logback-core/1.1.7/logback-core-1.1.7.jar among others.
• Click on the file.
• Issue is actually found in the LoginAuthenticator class.

Expected result

The filename includes the LoginAuthenticator class name and full path in the package tree.

This is how Windup displays issues within a JAR file, including class name and full path in the package tree:

Actual result

Only the JAR file name is displayed, not providing any coordinates about the class that contains the actual incidents for the given issue:

[pranavgaikwad]

This is now fixed with the changes to deps file URIs