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
I am using gradle-processes to manage a set of long running services.
I am basing my tasks on JavaFork, and simply using the main class with classpath and arguments.
On OSX, and Linux that works up the expectations, but on windows, the forked processes are dying on me after the build is finished.
:startMainApp
BUILD SUCCESSFUL
Total time: 1 mins 53.635 secs
C:\projects\git\development\master>
Any idea ? or any settings I need to set to avoid my separate process to be terminated when gradle exists ?
The text was updated successfully, but these errors were encountered:
I am using gradle-processes to manage a set of long running services.
I am basing my tasks on JavaFork, and simply using the main class with classpath and arguments.
On OSX, and Linux that works up the expectations, but on windows, the forked processes are dying on me after the build is finished.
Any idea ? or any settings I need to set to avoid my separate process to be terminated when gradle exists ?
The text was updated successfully, but these errors were encountered: