[BUG] containerless kantra needs to remove the exploded Java binary dir

[eemcmullan]

Is there an existing issue for this?

• I have searched the existing issues

Konveyor version

latest

Priority

Major

Current Behavior

No response

Expected Behavior

No response

How Reproducible

Always (Default)

Steps To Reproduce

No response

Environment

- OS:

Anything else?

No response

[konveyor-ci-bot]

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.

[AdityaPandeyCN]

Hi @eemcmullan hope you are doing well. I want to work on this issue, with my initial analysis I am thinking of an approach where we ensure exploded Java binaries are included in the a.tempDirs list for cleanup or adding explicit logic to clean them. I will be grateful for any specific guidance from you.

[AdityaPandeyCN]

Hi @eemcmullan I did another detailed analysis and I think we have to work with the analyzer-lsp codebase specifically the util.go where the Java binary dir are being exploded(https://github.com/konveyor/analyzer-lsp/blob/main/external-providers/java-external-provider/pkg/java_external_provider/util.go). What are your views?