-
Notifications
You must be signed in to change notification settings - Fork 36
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
Can not start Server on Windows #308
Comments
'Run on Tomcat Server' The app seems to be published to another webapps path, not the webapps path under Tomcat,‘Open in Browser' is 404 error . |
This appears to be an issue with the 0.11.3 release and this issue #277 |
quickest solution before bug if corrected, is remove workspace specific java.home on windows OR relocate to a directory without a space in the directory path to java. |
This is affecting me, too... @spdermn02 I don't have a workspace-specific |
If you have user-level configuration for those - then it's still an issue since your java is now full-pathed and contains a space. because it is in "Program Files" - if you installed java to a non-space separated folder structure it should still work, but by default since it installs to Program Files - it will now be a problem on windows. |
Also a current workaround to this problem is turn off auto-updates and then install 0.11.2 which was still working before the 0.11.3 version was published from the "develop" branch, and no official release was created in github. |
I tried, it is failed. webapps path is wrong |
I also uninstalled and installed the older version as per this stack overflow post and it resolved the issue for me for now. |
The problem is in spaces in path to Java binaries. I've changed |
Totally I'm having the same problem, is there any possibility that the line that executes directly to the console could append or format the directory for Windows paths? |
Steps to Reproduce:
Error msg:
[Tomcat 7.0]: 'E:\Program' is not recognized as an internal or external command,
operable program or batch file.
The text was updated successfully, but these errors were encountered: