You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi All,
I have been working on fixing few issues in this plugin since I use eclipse primary for my development. The reason for using eclipse is some of the projects or most of them, are really large projects and opening them in IJ takes lot of time and resources.
Now looking at this plugin architecture, it seems to take a similar approach like the groovy-eclipse does. But there are some roadblocks as well, such as expression evaluation and integration into DebugShell in eclipse.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi All,
I have been working on fixing few issues in this plugin since I use eclipse primary for my development. The reason for using eclipse is some of the projects or most of them, are really large projects and opening them in IJ takes lot of time and resources.
Now looking at this plugin architecture, it seems to take a similar approach like the groovy-eclipse does. But there are some roadblocks as well, such as expression evaluation and integration into DebugShell in eclipse.
So should we trying fix those issues some how ? Or should we all put our efforts on make the following LS for kotlin (https://github.com/fwcd/kotlin-language-server) and DA for kotlin (https://github.com/fwcd/kotlin-debug-adapter) and integrate it into Eclipse ?
additional feature which are not supported by LSP can be added as custom protocol messages into the language server.
WDYT ?
Beta Was this translation helpful? Give feedback.
All reactions