Another question that I would appreciate to have your feedback.
Debugging openhab with eclipse is a pain for me.
Many time, I have to wait several couple of seconds (>30 or 60s) when eating end points before I can do anything into eclipse debuger. Thread displaying is just frost.
I’ve also experienced lot of troubles with Expressions windows.
Display can take seconds to minutes to update.
When I try to expand complex expressions that contains maps for exemple, the display freeze for long times.
And even some times, after a few expands, it give me an exception, and have to refresh the expressions Windows, and restart my collections browsing.
I know that there are several reports on eclipse side about debuger issue, especially about the last one. And that it is not an Openhab issue, but more an eclipse issue.
But I just would like if others experience the same behavior in their dev environment.
And if sommes of you have some helpful hint to make the experience better.
After digging a lot this afternoon, take a look to lot of website talking about debugging issue in eclipse, and make lot of test on my installation, I find that the culprit is the size of the “Source Lookup Path”.
I’ve used to add this source Lookup path:
Using the Restore Default.
And adding all Workspace project to lookup.
As I work at same time on core, and on several addons, this make a quite large lookup set.
I’m not sure what is perfect for this configuration.
But I’ve find that removing existing entries, and adding Working set, Java Main Sources it’s far sufficient for almost most cases. And with that configuration, debugging is working quite instantaneous, no more freeze on displaying backtrace or in the Expressions window when browsing variables !
Of course, with this configuration you will not be able to step in .class files for external ressource. So perhaps we can find a better configuration.
But good to know that delay is coming from that.
I’m thinking to open a issue on eclipse side to tell them about this experience to see if there is some workaround / fixes that can help us on this.
