-
Notifications
You must be signed in to change notification settings - Fork 80
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
Wildcard imports of built-in packages don't work #4994
Comments
Eww. Why do we still have things that grep script imports? Regardless, I'm pretty confident that |
Lines 131 to 140 in e4d69fd
However, changing In GroovyDeephavenSession.createClassImport, after getDefinedPackage fails, ClassGraph is used to look up the class. ClassGraph has a specific config that must be applied to be able to scan system modules/packages - enabling that appears to resolve this. |
Also updates our classgraph build, in case we were affected by Java 17 issues. Fixes deephaven#4994
Also updates our classgraph build, in case we were affected by Java 17 issues. Fixes deephaven#4994
Also updates our classgraph build, in case we were affected by Java 17 issues. Fixes #4994
Also updates our classgraph build, in case we were affected by Java 17 issues. Fixes #4994
A wildcard import like:
throws:
This is basically because
groovyShell.getClassLoader().getDefinedPackage("java.util.concurrent")
returns null. (Using.getPackage()
, which is deprecated, does work. It eventually callsjdk.internal.loader.BootLoader.getDefinedPackage()
)The text was updated successfully, but these errors were encountered: