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

Does not recognize class names #89

Open
jlous opened this issue Apr 19, 2022 · 3 comments · May be fixed by #102
Open

Does not recognize class names #89

jlous opened this issue Apr 19, 2022 · 3 comments · May be fixed by #102

Comments

@jlous
Copy link

jlous commented Apr 19, 2022

Class names in my maven log are not linked, whether they are fully qualified, minimised-path or bare.
File names work fine.
I am pretty sure I have seen at least fully qualified class names linked before, albeit unreliably, considering #73.
But that was on Linux. I now have to use Windows, and see no trace, even when using old versions of the plugin.
Observed with both Java and Kotlin.

Links to failing tests in my maven builds would be a super-useful use case for this plugin.

Awesome Console 0.1337.12
IDEA 2022.3.3
Windows 10

@anthraxx
Copy link
Owner

Please provide an example log including a list of what you would expect to be clickable. Even for semi obvious cases, this makes my work of creating test cases and considering actual results lot easier compared to trying to reverse engineer what kind of log you were looking at.

@jlous
Copy link
Author

jlous commented Apr 20, 2022

Below is a minimal reproduction.
I would have expcected com.company.Main to link to the source file:

awesome

@jlous
Copy link
Author

jlous commented Apr 20, 2022

An added bonus would be if c.c.Main also worked, since this style of package compaction is common in logs

@anyesu anyesu linked a pull request Apr 14, 2024 that will close this issue
33 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants