-
Notifications
You must be signed in to change notification settings - Fork 51
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
Cleaning while executing libertyRun fails, then orphans the process with no way to shutdown #822
Comments
I see the following defined in
I am thinking the
|
yep, that seems to fix the issue, the right thing seems to be done if i add that. thanks for the quick response as always
|
I will follow up and see if we can add something to |
Interestingly, after trying to run a clean today with that workaround, i get the below issue. So maybe it's not an effective workaround by itself. had to disable the dependsOn it so i could clean it
|
Ok, good to know! |
I will be opening a PR for this shortly. In the meantime, the more correct workaround is the following:
And if you look at the |
Perfect, thanks for the better workaround. a good gem, hidden in the docs! |
I've been encountering this quite often unintentionally...if you have libertyRun being executed,
gradle clean
will fail because some files are in use...So you run libertyStop, but then it can't stop the server because the clean task already got rid of what was needed...Result: the build is both not cleaned, and the process is running in the background and has to get killed manually...
Expected: I'd expect
gradle clean
to realize that the server is running and fail & message with that. This should prevent it from cleaning files it needs and getting in a state it can't come back fromgradle plugin 3.5.2, gradle 7.x
The text was updated successfully, but these errors were encountered: