-
Notifications
You must be signed in to change notification settings - Fork 21
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
Problem developing on a remote PC #78
Comments
Sorry for the noise. I solved it. It was my misunderstanding of how to run a custom goal in Netbeans. |
@qzic thanks for solving and closing :-) |
Well I'm quite new to maven, have been using ant in netbeans for years. After setting up the two custom actions. I could find the Custom entry in the Project rt-click menu. Then I found Run Maven and it had the two custom entries remote run and remote debug. I have reopened the issue because although remote run works, remote debug does not.
It seems remote.platform.port has not been defined for/in the build.xml |
I made a little progress (might be the wrong path??)
I hadn't noticed this line so I updated it with my Netbeans defined remote platform
Now there are no errors but with a breakpoint set on the "Hello Rasbian" statement in Main.java this is the output
So it seems to be running but not hitting the break point. Is "Listening for transport dt_socket at address: 1955 When I try the Netbeans Debug button with this this project set as main project, here is what I see:
Also the debug toolbar shows up with the red debug stop button etc. |
I noticed that Remote Run and Remote Debug show up in the Netbeans action list for the project. So I copied the execute goals to Run and Debug which are activated from the main Run Debug buttons. I removed everything in the properties for Run and Debug except jpda.listen=true for Debug. Both buttons work and after clicking Debug, the Debug toolbar appears. Note that the 1st chunk of output "cd ..." references the jvm on my local windows??? Later we see it downloaded and running on the raspberry.
|
Duh! So I see that platform line in build.xml should be raspberry |
I have messed around with build.xml and I found I had to correct the <target name="-debug-remote-key" .... section because it was not using the some variables defined in raspberry.properties. Despite this I have the same result with it hanging Final output on remote debug (remote run is fine)
Here is the current build.xml which resolves all variables when running remote debug
|
Hi qzic, https://gitlab.fhnw.ch/ip_12_preparation/hellopi5.git It is used at our university. The README is in German. But with Google Translate you should be able to set up your laptop and the Raspberry Pi (a setup script for the RaspPi is also included). Essentially it's a Maven project. The whole setup is in the pom.xml . Even if IntelliJ IDEA is referenced, you don't need to use it. It should work fine with NetBeans as well. Greetings from Switzerland |
I think the pi4j-maven-archetype needs to be updated with the previous build.xml file (which works as it should) plus a fix for debug. |
I'm trying to run the pi4j archetype on a raspberry 5.0 from Windows 10 with Netbeans 24. I have set up the raspberry.properties and can run/debug it.
The problem is it runs on my local machine not on the raspberry.
I changed the first statement in main to
console.box("Hello
Rasbian world ! OS = " + System.getProperty("os.name")); I also commented out the code following this statement because it just caused a crash (because its running on the wrong platform).`
to figure out what was going on.
running with maven -X this is the final part of the output
The text was updated successfully, but these errors were encountered: