-
Notifications
You must be signed in to change notification settings - Fork 193
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
java.lang.NoClassDefFoundError: org/eclipse/jdt/groovy/search/TypeInferencingVisitorWithRequestor$1Helper #193
Comments
I noticed there is a "Non-Locking ClassLoader" bundled. Could that be the reason why the ClassDef for TypeInferencingVisitorWithRequestor$1Helper is not being found, even though it's adjacent to TypeInferencingVisitorWithRequestor? |
Does anyone have any idea why this is happening? We're also encountering the issue now on Eclipse Neon.1 (4.6.1) Thanks in advance |
Not sure what revision of Groovy-Eclipse you are picking up. But I have found support for 1.8 is likely not there in 2.9.2. |
I thought I saw a set of commits to fix Groovy 1.8 support, but I can't find it at the moment. If that gets in, I could update Groovy to 1.8.9 and further certify the current state of support for it. |
What's the reason for closing this issue? I'm still having the issue, it hasn't been resolved. |
Have you tried the latest 2.9.2 snapshot? Should be fixed. |
Ok, sounds good. I was able to give it a quick look through and it looks like it was fixed. Thanks! |
I've been banging my head against this issue for sometime. I've built a custom distribution of Eclipse, that is essentially GGTS + some extra plugins, and this error message is popping up constantly. I've checked the org.eclipse.jdt.groovy.core jar manually, and the .class file is there.
I'm referencing the Groovy-Eclipse plugin by using the following XML:
<plugin id="org.codehaus.groovy.eclipse" download-size="0" install-size="0" version="0.0.0"/>
This issue may end up being related to how the Groovy-Eclipse plugin is being installed in the custom distribution.
We are currently using Groovy 1.8 and Grails 2.1.5
Stack trace and more info below:
The text was updated successfully, but these errors were encountered: