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
On the Remote Host the Kotlin extension is installed (which obviously uses kotlin-language-serve)
Problem:
The setup itself works, but not very usable. For a project Im currently working on it takes almost 2 hours to resolve dependencies before the server initialised. When the init process is done, the extension works just fine. However, the 2 hours init process is performed every time I connect to the remote host (or restart the vs code).
Expected behaviour:
After a full successful initialisation I'd expect the server to use the resolved dependencies event after the restart, the dependencies update may be done in background, while the server uses the (cached?) result after the previous initialisation. If there is such a caching ability, it would be very useful to have the description of how to set it up on README.
The text was updated successfully, but these errors were encountered:
Yeah, caching the dependencies seems like a reasonable solution to this. Do you use Gradle or Maven? In case you use Gradle, a daemon should keep running in the background providing fast, incremental builds/dependency resolutions.
@fwcd I'm using Gradle, I think I've explicitly disabled daemons due to some issues, I'll give it a try with daemons a bit later. Thank you for the hint!
My current setup:
Problem:
The setup itself works, but not very usable. For a project Im currently working on it takes almost 2 hours to resolve dependencies before the server initialised. When the init process is done, the extension works just fine. However, the 2 hours init process is performed every time I connect to the remote host (or restart the vs code).
Expected behaviour:
After a full successful initialisation I'd expect the server to use the resolved dependencies event after the restart, the dependencies update may be done in background, while the server uses the (cached?) result after the previous initialisation. If there is such a caching ability, it would be very useful to have the description of how to set it up on README.
The text was updated successfully, but these errors were encountered: