-
Notifications
You must be signed in to change notification settings - Fork 190
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
Wildcards in classpath do not work anymore #834
Comments
Tested it on macOS and in GraalVM Docker containers. |
Confirmed. I think this was caused by the switch to thin language launchers. It was kind of working by accident before. You can work around it by doing the expansion yourself (via command line (shell) or We'll probably implement launcher support for this eventually, but it's not a priority for us right now. |
It seems that since GraalJS 22.x, wildcards in the classpath do not work anymore.
Before (21.x), I got this behavior:
with any later version (tested with 22.3.3, 23.0.2 and 24.0.1), I get this:
Java.addToClasspath()
with a wildcard does not work either:However, listing the jar files explicitly works:
It seems that before 22.x, the wildcard was expanded at some point:
After 22.x, the wildcard appears in the classpath as-is:
It does not seem to be a problem with GraalVM in general because when printing out the
java.class.path
in a Java program, it still gets expanded (the program simply printsjava.lang.System.getProperty("java.class.path")
):The text was updated successfully, but these errors were encountered: