Summary: | java.lang.ClassNotFoundException: org.codehaus.jdt.groovy.integration.internal.GroovyLanguageSupport at startup | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Mauro Molinari <mauromol> |
Component: | Core | Assignee: | Olivier Thomann <Olivier_Thomann> |
Status: | VERIFIED NOT_ECLIPSE | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | CC: | jarthana, Olivier_Thomann, remy.suen |
Version: | 3.5 | ||
Target Milestone: | 3.6 M7 | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Whiteboard: |
Description
Mauro Molinari
2010-04-08 07:05:00 EDT
This looks like a problem with the groovy plugins. Closing as NOT_ECLIPSE. Please report the problem to the groovy team. Ok, sorry, it seems that something (maybe the latest Spring IDE plugin) has installed "JDT Core patch for Groovy-Eclipse plugin" on my system by simply doing a "Check for updates" (not "Install new software"!) and I thought this were something by the JDT team rather than the Groovy Eclipse plugin team. I do not use Groovy, I do not need it and I never installed the Groovy Eclipse plugin on my system... So I just uninstalled it now, although I'm quite surprised that Eclipse didn't complain about some broken dependency (why p2 requested its installation if it doesn't seem to be needed by any other plugin in my system?). This is why I was confused. Mauro. My guess is that this JDT patch doesn't define its dependencies the way it should. You might want to check it to make sure that p2 doesn't have a bug. If dependencies look ok, then you should report a bug against p2. Otherwise you should report a bug against groovy for not specifying the right dependencies. Verified for 3.6M7. |