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

[craftercms] gradlew stop does not stop all the started processes in Windows #1768

luishernandezmonge opened this Issue Jan 13, 2018 · 1 comment



luishernandezmonge commented Jan 13, 2018

Expected behavior

The gradle stop should stops all the process that starts as part of the starting up of the environments
The system should be able to delete the craftercms folder after gradle stop
(Stills like in use by other process)

Actual behavior

The gradlew does not stop all the processes

Steps to reproduce the problem

  • Go to craftercms folder and run the next gradlew commands:
    gradlew.bat selfupdate
    gradlew.bat init
    gradlew.bat update
    gradlew.bat build deploy -P””
    gradlew.bat start
  • Try to stop craftercms
    gradlew.bat stop
  • Try to delete the craftercms folder, and notice that the folder stills on use by some process

Log/stack trace (use

watch the next video (gradlew stop and delete folder):



craftercms 3.0.x


MS Windows 2012 server
MS Windows 10


@sumerjabri sumerjabri added this to Backlog in Crafter CMS v3.0.x via automation Jan 15, 2018

@sumerjabri sumerjabri added this to the Crafter CMS v3.0.4 milestone Jan 15, 2018

@cortiz cortiz moved this from Backlog to In Progress in Crafter CMS v3.0.x Jan 16, 2018

@cortiz cortiz moved this from In Progress to Test & Validate in Crafter CMS v3.0.x Jan 18, 2018

@cortiz cortiz assigned luishernandezmonge and unassigned cortiz Jan 18, 2018


This comment has been minimized.

Show comment
Hide comment

luishernandezmonge Jan 18, 2018


Verified as resolved


luishernandezmonge commented Jan 18, 2018

Verified as resolved

Crafter CMS v3.0.x automation moved this from Test & Validate to Completed Jan 18, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment