When selecting the debug deploy option in eclipse, the build appears to happen but the debugger fails to connect to the remote target.
https://www.chiefdelphi.com/forums/showthread.php?t=153511 lists out another user with the same symptoms. Although the debug-deploy ant target appears to build fine, the launching of the debugger drops into this loop and continues through all available attempts before giving up. RIO can be found over MDNS (that's what the deploy uses).
I am curious if the ant build call here is guaranteed to let the ant build finish before it returns. I haven't yet set up the environment to build/debug the plugin to find out.
We replicated this issue on two different PC's, and suspect it is present on a third...
For now, we are working around it by either using printf's, or manually starting the JVM on the RIO with the right debugger flags and manually setting eclipse to connect to the remote machine.
Tests were done with a fresh, new, unmodified IterativeRobot project
When selecting the debug deploy option in eclipse, the build appears to happen but the debugger fails to connect to the remote target.
https://www.chiefdelphi.com/forums/showthread.php?t=153511 lists out another user with the same symptoms. Although the debug-deploy ant target appears to build fine, the launching of the debugger drops into this loop and continues through all available attempts before giving up. RIO can be found over MDNS (that's what the deploy uses).
I am curious if the ant build call here is guaranteed to let the ant build finish before it returns. I haven't yet set up the environment to build/debug the plugin to find out.
We replicated this issue on two different PC's, and suspect it is present on a third...
For now, we are working around it by either using printf's, or manually starting the JVM on the RIO with the right debugger flags and manually setting eclipse to connect to the remote machine.
Tests were done with a fresh, new, unmodified IterativeRobot project