Unify error and warning locations reporting in the console
- Dominant language
- Java
- Stars
- 14.6k
- Forks
- 7k
- PR merge metrics
- No merged PRs in 30d
Description
At the moment, Compiler.java rewrites the location of an error (elision of the absolute file path), while leaving the location of a compiler warning in its raw form.
Would be nice to have all the paths elided, no?

Doing this would also simplify the task of jumping to warning locations from the console, as has been requested in #3383
Contributor guide
Research direction
Start by reading Compiler.java and compare how compiler errors and warnings are formatted before reaching the console. Make the warning location handling consistent with error reporting so absolute paths are elided, then verify that both message types show the shortened locations and remain usable for console navigation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100