-
Notifications
You must be signed in to change notification settings - Fork 9
Strange errors in IntelliJ (Possible collision / interference with Lombok) #30
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
Comments
Can you try |
Yeah that works, IntelliJ will pick up the class files generated via the Gradle build, and oddly enough you can even change those classes one at a time and incremental compilation seems to work. Doing a rebuild in IntelliJ causes the problem to re-emerge though. |
@johnmcclean-aol after that I also did a |
Yeah that would also work, what I mean though is it doesn't help IntelliJ do the compilation itself. It can read the class files generated by javac called via Gradle. |
but after a "./gradlew clean" there should be no "class files generated by javac called via Gradle" left, no? will check in more details tonight though. |
Ah, sorry - I see what you mean now. I was running clean compile. Let me give that a try.. |
that may be related to the order processors will run? if so some changes are needed to have it working with lombok: |
Hey guys,
I'd like to turn on this feature in cyclops-react (aol/cyclops#347), when I added the hkt project as a dependency and make cyclops-react Higher class extend org.derive4j.hkt.__ everything compiles just fine from the command line. Unfortunately, IntelliJ starts showing some strange errors instead.
Lombok's val will generally fail, but other errors seem unrelated and really strange. I've attached a screenshot where the line numbers of some spurious compile errors have been misattributed.
I'm not sure how easy or hard it would be to fix this (as the issue may well be on the IntelliJ side or Lomboks), but I thought you'd appreciate getting a report of it.
Thanks,
John
The text was updated successfully, but these errors were encountered: