This repository has been archived by the owner on Nov 3, 2024. It is now read-only.
PsiInvalidElementAccessException PluginException from ChangeMethodSignatureFromUsageFix #649
Labels
Comments
|
Having this as well, posting my case in case it helps diagnosing the issue: IDEA: 2019.2 |
|
Same stacktrace as #634 |
|
Environment: Plugin version: Might be related: And then following errors: |
|
Catched today with 0.27-2019.2. |
|
Seems to be the same issue with 2019.2.3 To be exactly sure i will link the stack trace as well Happened out of the box, when modified a field variable and marked it with a Hope it helps. |
|
@mmoayyed Your stacktrace is related to lombok project (this one https://github.com/rzwitserloot/lombok). |
|
I don't think that is true. The project builds just fine from the command-line with lombok. It only has problems building in IDEA. |
|
@mmoayyed. Okey, lets check) Disable Lombok plug-in and run the build without plugin support. In your stacktrace I see that exception was thrown from Lombok annotation processor. And no one line about idea-Lombok plugin from current project. |
This can't be done for obvious reasons. The project requires the lombok plugin to build, and it does so just fine with previous versions of the IDE. Using the below IDE version and latest version of the plugin, I am no longer seeing the error: Thank you @mplushnikov for the latest patches! |
|
@mmoayyed Which “obvious reasons”? You just need to enable annotation processing support to enable Lombok support in your IDEA. If you use maven I guess all configuration will be done for you. |
mplushnikov
changed the title
This was referenced Dec 1, 2019
|
|
This was referenced Feb 26, 2020
This comment has been minimized.
This comment has been minimized.
|
@keruzk which version of Lombok Plugin are you using? unless you are on EAP, Lombok Plugin isn't compatible with IntelliJ 2020.2 yet (I faced the same issue this morning). |
|
@quiram ooh, indeed you're right. I am using |
|
Thanks, donwgrade should solve. |
This was referenced Aug 12, 2020
Closed
Closed
Closed
|
When the lombok plugin crashes, it disables the saving of files. I manually save with command-s to enable formatting and have lost work due to this behavior. If the fix is hard, is there a way to provide an interim that makes the crash less obnoxious? |
|
same issue Lombok (0.30-2020.1) |
This comment has been minimized.
This comment has been minimized.
|
Please disregard my message, as it's not applicable to the issue on further review. |
|
2020.2.1 is out and Jetbrains tells us that they fixed the lombok problem. |
|
@ruurd @jameschensmith This issue has nothing to do with #829 |
|
@mplushnikov, ah, sorry about that. I thought it was the platform issue. I'll update my comment in order to not confuse people reading this issue. |
|
@mplushnikov With due respect, may I know, why my issue was masked as off-topic? |
|
@subhrajlahiri This issue is about an exception in "ChangeMethodSignatureFromUsageFix". This is an old problem. |
mplushnikov
changed the title
|
@mplushnikov Hi! New exception with Version information IDEA: 2020.2.1 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Today was exception (don't know why):
Version information
IDEA: 2019.2
JDK: JDK 11.0.3
OS: Windows 10
Lombok plugin: 0.25-2019.1
Lomok: 1.18.8
The text was updated successfully, but these errors were encountered: