-
Notifications
You must be signed in to change notification settings - Fork 62
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
Silk workbench cannot be started on Windows #62
Comments
Hi Silk Devs, Even I am having this issue. Long list of class names can be resolved by simply adding new line char. However, it fails in finding the class, play.core.server.NettyServer. Can someone please suggest a workaround? I tried 2.6.x and I am getting same issue. Nilay |
Hi, this is an issue of the sbt native packager that is used by the Play java -cp "lib/*;" play.core.server.NettyServer . Cheers, [1] sbt/sbt-native-packager#72 On Tue, Nov 1, 2016 at 10:57 PM, Nilay Chheda notifications@github.com
|
Thanks Rob. This seems to be working. I also have one more query. After starting play server, how do I actually start a silk workbench application? In the documentation, only information available is to run command However, that is resulting in the following error: I am not sure what I am missing here. Thanks for the help. |
By the way, same error I am observing on my virtual machine running latest Fedora distro. So this issue seems to be platform agnostic. |
Did you solve the issue? I am getting the same problem. |
The silk-workbench.bat script in silk-workbench-2.7.1 tries to set the classpath to a very long list of jars. This line is too long as windows will complain "input line too long". Using a wildcard instead does not solve the issue.
Also, when setting the classpath in multiple lines, the line where the workbench is actually started fails too since it cannot find the main class.
The text was updated successfully, but these errors were encountered: