-
Notifications
You must be signed in to change notification settings - Fork 7
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
Restart server on build changes #11
Comments
I played with this for couple of hours and unfortunately, couldn't make it to work. Like you said, it re-compiles just fine but the server restart isn't happening. Looking around it looks like a common issue. I'll keep digging into it further as this annoys me too but I can't promise to fix this right away. Eventually I'd like to actually write a plugin for https://github.com/HotswapProjects/HotswapAgent, which may be better anyway. You probably already know this but you don't need to restart the server for assets changes. Here's the doc that explains it what you have to do: https://alpas.dev/docs/mixing-assets#watching-changes-and-auto-reloading |
I have setup a project using
alpas init myapp.web
.I have then successfully started the server using
alpas serve
(also triedalpas watch
).I then change the default
WelcomeController
but changes are not picked up even with a separategradle build --continuous
(which does pick up changes and recompile).Let me know if you need further info.
What I would expect is the server to restart when new changes are detected in
build
, ideally to not restart unnecessarily when, for example, asset changes are detected.The text was updated successfully, but these errors were encountered: