-
Notifications
You must be signed in to change notification settings - Fork 41
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
Server stops immediately when runPlay is run from another tasks #158
Comments
I think I've reproduced this within the same project and can't yet grasp the issue here:
seems to be simple approach to debugging, but play stops immediately. |
And it was pretty easy to get what's happening from here. Not sure this can be / should be fixed in plugin (however debug task would be nice) |
Does this mean you all are able to set debug breakpoints using this setup? I'm trying to get the same going over command line with : [UPDATE]
if you don't want the daemon to wait for connection just flipt the jwdt suspend to n: |
@yfeleke long time passed but maybe you remember if you did this and used the remote debug in intellij or simply local debug ? Thanks |
Gradle 6.6.1. Version 0.10
Not sure what's going on here. The application runs fine from the distribution tar and if runPlay is called directly. I can see that the server starts and that port 8080 is bound but then
PlayWorkerServer::stop()
is called.I can't reproduce this is the task that calls the
runPlay
task is in the same project.The text was updated successfully, but these errors were encountered: