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.

Sign up for GitHub

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

Jump to bottom

[Backport] Improve causalilty reporting for unresolved elements #32

Closed
zakkak opened this issue Dec 17, 2024 · 0 comments · Fixed by #34
Closed

[Backport] Improve causalilty reporting for unresolved elements #32

zakkak opened this issue Dec 17, 2024 · 0 comments · Fixed by #34
Assignees
@zakkak
Labels
backport Backport or backport request
Milestone
23.1.6

Comments

@zakkak
Copy link
Contributor

zakkak commented Dec 17, 2024

What would you like to backport?

oracle/graal#10320

Describe the motivation for the backport.

This PR resolves oracle/graal#6253 which makes it very hard for users to understand why an element is reported as unresolved despite being on the classpath.
@zakkak zakkak added the backport Backport or backport request label Dec 17, 2024
@zakkak zakkak self-assigned this Dec 17, 2024
@zakkak zakkak added this to the 23.1.6 milestone Dec 17, 2024
@zakkak zakkak mentioned this issue Dec 17, 2024
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@zakkak zakkak

Labels
backport Backport or backport request
Projects
None yet
Milestone
23.1.6
Development

Successfully merging a pull request may close this issue.

[Backport] Improve causalilty reporting for unresolved elements zakkak/graalvm-community-jdk21u
1 participant
@zakkak