| Summary: | [refactor][lombok] Lombok generated logger with custom name cannot be resolved during local variable extraction | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Giacomo Baso <giacomo.baso> |
| Component: | Core | Assignee: | JDT-Core-Inbox <jdt-core-inbox> |
| Status: | CLOSED NOT_ECLIPSE | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | derJoerg, lhozdroid, loskutov |
| Version: | 4.20 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
|
Description
Giacomo Baso
Issue still present in Eclipse 2021-06 Happening again after 23-03 (4.27.0) update. Using Lombok 1.18.24 Same here. Happens with Eclipse version 2023-03 (4.27.0) and lombok version 1.18.26. Lombok is processed. I can see the generated logger object in the outline view, but it has the wrong name. So this particular setting is apparently not respected. Two notes: 1) please report the issue to Lombok, this is the (old) bug tracker of JDT which has no relationship to Lombok at all. 2) If you believe this *is* JDT issue, please create a bug with *detailed* description how to reproduce and why this is a JDT problem at https://github.com/eclipse-jdt/eclipse.jdt.core/issues/ thanks for your comment. I thought it was probably a regression, but there is indeed an open issue at lombok right now which fits: https://github.com/projectlombok/lombok/issues/3332 kind regards |