Stream: committers
Topic: Debugging the build
Rik Smithies (Jun 02 2021 at 16:50):
I had a problem today where I changed an attribute name on a resource, and it caused the local build to crash. No helpful error message and not easy to diagnose even though I knew the cause. I eventually realised I had to update a search parameter to match. But how could I have diagnosed this? I'm not a Java person normally but can I run the build within NetBeans or Eclipse or something, to step the code when it crashes?
Lloyd McKenzie (Jun 02 2021 at 17:24):
Getting the build to run is semi-involved. You need some Eclipse plugins, plus you can't use the 'current' HAPI code because that's always one version off the version the publisher relies on. Simplest thing is just look at the java file implicated in the stack trace. 50% of the time, just looking at the code location will give you some solid insight into what's wrong. If you want to run the build in Eclipse, there's some guidance here on how to set up your environment. If/when you run into trouble, @Mark Iantorno is great at helping to trouble-shoot.
Mark Iantorno (Jun 02 2021 at 17:33):
I have fixed this
Mark Iantorno (Jun 02 2021 at 17:33):
It should not require those steps anymore
Mark Iantorno (Jun 02 2021 at 17:33):
it should work
Mark Iantorno (Jun 02 2021 at 17:33):
I'm going to update the documentation to reflect this
Mark Iantorno (Jun 02 2021 at 17:53):
@Rik Smithies if you're just doing one off changes in the libraries to solve an error here and there do not use eclipse
Mark Iantorno (Jun 02 2021 at 17:53):
use intellij
Mark Iantorno (Jun 02 2021 at 17:53):
https://www.jetbrains.com/idea/download/
Mark Iantorno (Jun 02 2021 at 17:53):
the free community edition is more than enough functionality for most professional developers, and should more than do what you need
Mark Iantorno (Jun 02 2021 at 17:54):
it will work more consistently and be easier for me to support you'
Last updated: Apr 12 2022 at 19:14 UTC
