-
Notifications
You must be signed in to change notification settings - Fork 29
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
Task startServer Hangs #20
Comments
+1 seeing the same issue, and no lock file is being created. |
Same here |
@georgepapas and @brookslyrette - I'm facing the same issue. Did you find any solution for it? thanks |
I had the same issue and I think I found out why it is happening. The "ready" directive means it is waiting for the string that you pass to it to appear on standard out. So you will have to specify something your "startApplication.bat" is printing on standard out when it is finished starting. For example, if you have a program which prints "I am a server, I run now on port 8080", you will have to use At leas that was what I did wrong and once I fixed it the plugin worked like a charm. Here is the relevant code from the plugin itself:
HTH |
I also have a similar issue. When using 0.6.0 my tests continue after Spring Boot has started. Using 0.8.0, it just hangs for some amount of time between 2 and 8 minutes, then will continue. No changes other than the version. |
Build is hanging at startServer.
It is not going ahead to execute remaining tasks.
build.gradle:-
apply plugin: 'com.wiredforcode.spawn'
task startServer(type: SpawnProcessTask, dependsOn: 'assemble') {
command "startApplication.bat"
ready 'Started.Application'
pidLockFileName ".new.pid.lock"
}
task stopServer(type: KillProcessTask)
cmd Output:-
The text was updated successfully, but these errors were encountered: