-
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
Groovy JDK classes not supported by default #1046
Comments
This is because Groovy 2.5 broke up the groovy-all jar into multiple jars. If you want to use the DGM "plus(Date, int)", you need to add groovy-dateutil library to your project or to your |
The "Invalid Registry Object" is a known issue. I have a workaround: #981 (comment) and I have a fix that is yet to be merged: https://git.eclipse.org/r/#/c/155098/ |
Thanks for the fast answer :-) |
I think the maintainers of Groovy are trying to push a switch to DateTime from Date. The extension methods for DateTime are present out of the box. |
I use the configuration:
A simple Groovy script, created in a new Groovy Project:
results in:
caught: groovy.lang.MissingMethodException: No signature of method: java.util.Date.plus() is applicable for argument types: (Integer) values: [1] Possible solutions: parse(java.lang.String), is(java.lang.Object), split(groovy.lang.Closure), use([Ljava.lang.Object;), wait(), clone()
When I switch to Groovy Compiler Version 2.4.1.8, the Groovy script is running correctly and shows the expected result!
After the compiler switch, the Eclipse windows are destroyed (errors like "Failed to create the parts controls", "Invalid registry object", read crosses) but I can reopen them.
The same problem happens for Java8 or Eclipse 4.8.0 or Compiler Level 2.5.9.
I guess this as a bug. I would expect that the plugin supports the Groovy JDK classes by default.
Thank You!
The text was updated successfully, but these errors were encountered: