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] Maven failure are not shown to the user #424

Open
1 task done
ascheman opened this issue Nov 15, 2023 · 2 comments
Open
1 task done

[BUG] Maven failure are not shown to the user #424

ascheman opened this issue Nov 15, 2023 · 2 comments
Labels
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. priority/backlog Higher priority than priority/awaiting-more-evidence.
Milestone

Comments

@ascheman
Copy link
Contributor

Is there an existing issue for this?

  • I have searched the existing issues

Konveyor version

analyzer-lsp: 37c4e3e

Priority

Major

Current Behavior

When a Maven build fails, the only output is

  • INFO[0009] unable to get dependencies, using fallback error="{}" provider=java when the dependency parser fails (cf. [BUG] Maven Dependencies are not (always) correctly parsed #392)
  • unable to get dependencies (none found), using fallback when the dependency analyzer does not produce any output (for whatever reason)
  • failed to download dependencies, continuing to download sources when Maven cannot (completely) download binary artifacts (aka. resolution)

In none of these cases we see the original output of the background Maven process. Therefore, we cannot analyse the root cause.

Expected Behavior

Show the (full) output of the Maven process, at least when debug logging is switched on.

How Reproducible

Always (Default)

Steps To Reproduce

It is necessary to have a suitable project / or test case.
Will try to provide something with an upcoming PR.

Environment

No response

Anything else?

No response

@ascheman ascheman 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 Nov 15, 2023
@ascheman
Copy link
Contributor Author

Test cases provided by #427 will showcase some of the behaviour above.

@pranavgaikwad pranavgaikwad removed the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Jan 25, 2024
@github-project-automation github-project-automation bot moved this to 🆕 New in Planning Jan 25, 2024
@dymurray dymurray added this to the v0.5.0 milestone Jun 20, 2024
@dymurray dymurray moved this from 🆕 New to 📋 Backlog in Planning Jun 20, 2024
@dymurray dymurray modified the milestones: v0.5.0, v0.6.0 Jul 18, 2024
@dymurray dymurray added the priority/backlog Higher priority than priority/awaiting-more-evidence. label Jul 18, 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-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Jul 18, 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-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. priority/backlog Higher priority than priority/awaiting-more-evidence.
Projects
Status: 📋 Backlog
Development

No branches or pull requests

3 participants