Open egaga opened 9 years ago
I see the same behavior with appRun
when there is an error on startup - ERROR Error starting server
. My expectation would be that the container would be stopped:
gradle -version
------------------------------------------------------------
Gradle 2.8
------------------------------------------------------------
Build time: 2015-10-20 03:46:36 UTC
Build number: none
Revision: b463d7980c40d44c4657dc80025275b84a29e31f
Groovy: 2.4.4
Ant: Apache Ant(TM) version 1.9.3 compiled on December 23 2013
JVM: 1.8.0_60 (Oracle Corporation 25.60-b23)
OS: Mac OS X 10.10.5 x86_64
plugins {
id "war"
id "org.akhikhl.gretty" version "1.2.4"
}
gretty {
httpPort = 5656
scanInterval = 2
reloadOnClassChange = true
reloadOnConfigChange = true
servletContainer = "jetty9"
}
Running
gradlew farmIntegrationTest
works perfectly unless some exception occurs.When integrationTest gradle-task fails, then the container (e.g. jetty) stop command is not run. So after next
gradlew farmIntegrationTest
the webserver is running, and the gretty prematurely has to end its process.The gretty workflow for integration test does not specify how errors are handled.
See the gradle log with a protractor nodejs task.
The configuration file: