Is anyone else having issues with the java debug deploy option this year?
We are using eclipse Neon on windows 10, 64 bit. We can create a brand new iterative robot project (leaving the boilerplate code in) and deploy it without issue to the RIO.
However, the debug deploy does not appear to do anything. Eclipse flips over to the debug perspective, but we get no console output, nor does the RIO appear to restart. Nothing shows up under any of the debug window panes....
Anyone else seen this yet? Or if not, and ideas on where to start debugging?
Thanks!
EDIT: Installed ant 1.9.7 independently on my computer, and ran "ant debug-deploy" in the root directory of the project. Got the following output:
Code:
...
compile:
[echo] [athena-compile] Compiling src with classpath=C:\Users\Chris Gerth\wpilib\java\current\lib\WPILib.jar;C:\Users\Chris Gerth\wpilib\java\current\lib\NetworkTables.jar;C:\Users\Chris Gerth\wpilib\java\current\lib\opencv.jar;C:\Users\Chris Gerth\wpilib\java\current\lib\cscore.jar to build
jar:
[echo] [athena-jar] Making jar dist/FRCUserProgram.jar.
[echo] [athena-jar] Copying jars to build/jars.
get-target-ip:
[echo] Trying Target: roboRIO-1736-FRC.local
[echo] roboRIO found via mDNS
dependencies:
[echo] roboRIO image version validated
[echo] Checking for JRE. If this fails install the JRE using these instructions: https://wpilib.screenstepslive.com/s...ller-java-only
[sshexec] Connecting to roboRIO-1736-FRC.local:22
[sshexec] cmd : test -d /usr/local/frc/JRE
debug-deploy:
BUILD FAILED
C:\Users\Chris Gerth\wpilib\java\current\ant\build.xml:192: required attribute libs.deploydir not set
Total time: 7 seconds
D:\RobotCasserole\eclipseWorkspace2017\TestEmptyProject>
Looking at that line, it would appear in fact that libs.deploydir is not set..... is this possibly a version of ant thing?
Edit2: Confirmed that by editing C:\Users\Chris Gerth\wpilib\java\current\ant\build.xml to have the same libs.deploydir that the debug target has gets the build to complete successfully. Seems to be working in eclipse too, although I have to manually relaunch the Remote Java Application on the RIO to start debugging. To Github to post a PR!