Windows client appears mute #13
Comments
Incidentally we also tried the Windows binary as shipped by JRuby - again mute. |
Thanks for looking into it! Please let me know what else you find. |
I doubt you meant to close an issue that is current? Could you reopen please (I have no such button)? |
Oops, your right. I did not mean to close it. Thanks. |
Guys, any update on this issue? |
I tried to debug C-source a little bit and it seems that inside |
I am also having this issue (win7 64bits). Please help.... (thanks!) |
I've recently checked in a number of win32 fixes, do you have these problems with the current tip of master? |
Also, do the examples work for you? I tested the Heartbeat, Echo and HelloWorld examples on a 64 bit windows 7 box. |
When I launch the examples, nothing happens. Here is how I do this (to make sure I am doing this right): |
It appears to work with latest changes from @jimpurbrick. Great job!!! Thanks!!! Tested on Echo and HelloWorld. By the way, the correct way to test is: |
I downloaded the latest sources from github, recompiled using "mvn clean install" as stated in the startup manual. I recompiled the ng.exe using the command above ( java.lang.ClassNotFoundException: com.martiansoftware.nailgun.examples.HelloWorld And the server side says: I am getting closer, I guess... Would anyone know what I am missing here? |
PS: I also tried to run the client using the command: |
PS2: Nevermind, I think I got my solution. The proper way to launch the client on the examples is using the following command: |
@bouteill you could avoid all that stuff with |
Well, I kind of like the idea to be able to separate: |
Everyone happy with me closing this now? |
Has there been a release? Or are you asking if you can mark this as fixed I've not had time to download and test yet. On 13 November 2013 12:40, Jim Purbrick notifications@github.com wrote:
|
Closing all issues older than 6 months; please reopen if it is still relevant |
We built clients for both Linux and Windows. The Linux one behaves as expected, the Windows one does not print the results of commands at all.
The Windows client happily prints the help content and that of version, but does not print things like classpath contents.
Stepping through the server we can see both clients executing code as expected and both clients receive network traffic so we're a little puzzled why one prints the returned value but the other does not. Continuing to investigate this...
The text was updated successfully, but these errors were encountered: