-
-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Lombok 1.16.4 breaks quickfix on eclipse mars RC3 #861
Comments
👤 [email protected] 🕗 Jun 20, 2015 at 05:22 UTC What steps will reproduce the problem?
What is the expected output? What do you see instead?
What version of the product are you using? On what operating system?
Please provide any additional information below.
|
👤 [email protected] 🕗 Jun 20, 2015 at 05:22 UTC |
👤 [email protected] 🕗 Jun 24, 2015 at 18:08 UTC I checked against eclipse mars, the released version. Unfortunately, the same issue exists. |
👤 reinierz 🕗 Jul 01, 2015 at 02:13 UTC The fix for issue #398 is causing this. Specifically, the pos fixer for retrieveRightBrace, found in PatchFixes' fixRetrieveRightBraceOrSemiColonPosition, is being applied to 'fix' the positions of some imaginary code that the quickfix tool is trying to display to help in showing what's going to happen here, and this causes the crashes. Note that these occur even if zero lombok anything is in your source file. The relevant stack trace for when fixRetrieveRightBraceOrSemiColonPosition kicks in but should not, is this:
and this stack trace is the 'top' either on hitting CTRL+1 or on trying to apply it. We can disable this patch but that would re-break 325. We need to be smarter about when to fix and when to skip it, or alternatively we need to fix what this meant to fix (325, amongst other things) elsewhere. |
👤 [email protected] 🕗 Jul 12, 2015 at 05:29 UTC Tried with latest git master containing 75647ee "Fixes for eclipse mars." but unfortunately the quickfixes still don't work. |
End of migration |
Migrated from Google Code (issue 826)
The text was updated successfully, but these errors were encountered: