Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Containerless-Kantra : [Windows-Only - Java binary analysis] Fails to decompile class files and creates incidents on the dependencies from .m2 #364

Open
1 task done
kthatipally opened this issue Oct 29, 2024 · 1 comment
Labels
kind/bug Categorizes issue or PR as related to a bug. needs-priority Indicates an issue or PR lacks a `priority/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@kthatipally
Copy link
Contributor

Is there an existing issue for this?

  • I have searched the existing issues

Konveyor version

https://github.com/konveyor/kantra/releases/tag/v0.6.0-alpha.2

Priority

Undefined (Default)

Current Behavior

I have run the analysis using the command:

./kantra analyze-bin --input ./airsonic.war --output ./output-war --target cloud-readiness --overwrite

The report is generated successfully.

I see errors in the log:
level=error msg="failed to decompile file" error="fork/exec bin/java: no such file or directory" logger=decompileWorker-1 provider=java

From the static-report, all the generated 4430 incidents are from .m2 folder and from known open source libraries.

Investigation of the issue:

  1. maven.default.index file is missing in the dependencies
  2. analyzer-lsp unable to find fernflower.jar

Expected Behavior

The war file is extracted, and all the class files are decompiled and analyzed successfully.

How Reproducible

Always (Default)

Steps To Reproduce

  1. Linux
  2. ./kantra analyze-bin --input ./airsonic.war --output ./output-war --target cloud-readiness --overwrite

Environment

  • OS: Ubuntu

Anything else?

No response

@kthatipally kthatipally added kind/bug Categorizes issue or PR as related to a bug. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Oct 29, 2024
@konveyor-ci-bot
Copy link

This issue is currently awaiting triage.
If contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.
The triage/accepted label can be added by org members.

@konveyor-ci-bot konveyor-ci-bot bot added the needs-priority Indicates an issue or PR lacks a `priority/foo` label and requires one. label Oct 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. needs-priority Indicates an issue or PR lacks a `priority/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
None yet
Development

No branches or pull requests

1 participant