-
Notifications
You must be signed in to change notification settings - Fork 6
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
Feature - use groovyserv cleint. #18
Comments
LT already has a Groovy server that does evaluations just like groovyserv (which is to say that LT's architecture is client/server). So I don't see how unless you mean for the scenario that LT is being repeatedly launched, exited, and relaunched and you want to shorten the startup time. |
Everytime I pressed CTRL+ENTER a gradle build started but I recieved no Was just using a basic hello world test. Sayth
|
Ah, I see. Haven't tried out the new Gradle stuff myself. Gradle has a --daemon switch which is probably the thing that needs setting if it isn't already. |
A couple of things:
Couple of questions:
To me it sounds that performance might not be the issue, but rather the fact that you are getting no results. Typically if the groovy server keeps dying each time you evaluate some code, it would incur the startup cost of firing up a new jvm, but you wouldn't get any results back. |
groovy evaluation
16:45:07.536 INFO lt.groovy.LTConnection - Before json: [null, gradle.err, On Wed, Jun 18, 2014 at 2:49 PM, Magnus Rundberget <notifications@github.com
|
Ah. Got it. And its bad, cause this should have been tested; What's happening is that when you have a .groovy file and try to evaluate it (without a previous connection) it will create a new connection. The logic for checking whether you try to connect to a gradle project or not, checks for the presence of a path argument. When you evaluate a saved .groovy file it sends the path of the file as an argument. So in your case it believes /home/sayth/Scripts/test.groovy is a gradle project. It tries to connect to that through the gradle tooling api and that fails (obviously). It fails spectacularly bad So I will need to create a fix. My bad. Sorry. There are two possible workarounds for now:
|
I have created a separate issue: #19 I'm closing this, cause Its highly unlikely that I will ever support groovyserv because It's already a server and pretty fast as well (once you actually manage to connect that is). |
Is there a way to use groovyserv with this LT plugin to give quicker response?
http://kobo.github.io/groovyserv/
Its easily installed via GVM.
The text was updated successfully, but these errors were encountered: