IntelliJ 2017.1.5 - Groovy debug - Class not found error
Answered
Earlier version of IntelliJ idea 2016.3.6 works with debugging java/groovy code with "Evaluate Code" mode on Groovy and recognising all classes from the classpath.
Whereas upgrading to 2017.1.5, it doesn't seem to and throwing "Class not found".
Let me know if there's patch / workaround for this, as I use this quite often for debugging Java/Groovy with "Evaluate Code" mode and selecting "Groovy" which now doesnt seem to work with my project.
Please sign in to leave a comment.
Please try 2017.2 release. In case the issue persists, please file a bug at https://youtrack.jetbrains.com/issues/IDEA and provide the steps to reproduce it.
I tried downloading 2017.2 and managed to reproduce the same issue.
Steps:
1. Java/Groovy application with maven dependencies
2. Debug with "Evaluate Code" on Java/Groovy
3. Try findAll/collectAll with "instanceof" $mavenDependentClass. For eg: list.findAll{it instanceof $dependentClass}
4. Class not found.
This happens both in Java/Groovy. Any idea, if default for debugger changed from 2016.3. This is totally working in 2016.3 but not in 2017.2 or 2017.1.
Hi, it would help a lot if you attach a sample project, thanks! And if possible, create a bug: https://youtrack.jetbrains.com/issues/IDEA
Hi,
The issue appears to be IntelliJ settings been changed on migrating to 2017.x.
So, when I debug with Java, I see loads of "package does not exist".
Few google search indicates, possibly some intellij settings / invalidate cache (which I done but no use).
Any thoughts on workaround or solution ?