-
Notifications
You must be signed in to change notification settings - Fork 21
Upgrade all demos and guides to 25.0.0.
#54
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
Conversation
cb590b9 to
6720c11
Compare
jirkamarsik
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
GraalWasm changes look good, thanks!
| public static void main(String[] args) throws IOException { | ||
| // Find the WebAssembly module resource | ||
| URL wasmFile = App.class.getResource("floyd.wasm"); | ||
| Source source = Source.newBuilder("wasm", wasmFile).name("example").build(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can drop .name("example") as the Source name is no longer used when reading the exports.
| </executions> | ||
| <configuration> | ||
| <mainClass>com.example.App</mainClass> | ||
| </configuration> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I always get tripped up by <pluginManagement> vs <plugins>. If I understand correctly, in <pluginManagement> we should only have the version, and the configuration should live in <plugins>, as in graalwasm-embed-c-code-guide.
This PR updates all demos to the new 25.0.0 releases of GraalPy, GraalJS, GraalWasm, and Espresso. This also requires updates for Gradle to run on JDK 25, as well as some adjustments for how Wasm modules are now instantiated on GraalWasm. Review commit-by-commit.