|Debugging: source lookup for dynamically compiled & loaded classes [message #1755355]
||Thu, 02 March 2017 15:37
| Witold Rojek
Registered: March 2017
I'm currently trying to solve a peculiar problem.
We are using Eclipse to write groovy scripts, which are installed in a database of an enterprise application running in Tomcat. The application is provided to us, so we are not developing it, merely modifying its behaviour via configuration and scripts. Those scripts are dynamically compiled and loaded by the said application.
We can remotely debug the application, we can set breakpioints in the scripts and everything works fine. The only problem is that eclipse refuses to lookup the sources no matter where we put them in the project and how we configure the lookup paths.
The problem was described in detail on Stack Overflow some 3 years ago and there seemd to be no solution to it:
Title of StackOverflow post:
Understanding Eclipse debug source lookup with dynamically compiled and loaded code
I wonder if this is such a rare usecase that it is not going to get any attention from eclipse developers.
The problem also doesn't make debugging impossible, it makes it just annoying to have to manually open the appropriate script and look for a specific line of code.
The company which developes our application uses InteliJ and the code lookup works fine there, so it is not a problem with the way the application loads the classes. It seems to be a specific problem of Eclipse.
Any information concerning the issue would be much appreciated, we love our Eclipse and would be sad if we'd had to switch to other IDE.
Powered by FUDForum
. Page generated in 0.01550 seconds