-
Sub-task
-
Resolution: Delivered
-
P4
-
24.0.2, 25
-
generic
-
generic
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8349738 | 24.0.2 | Marc Palmerjohnson | P4 | Resolved | Delivered |
Starting with JDK 25, `jpackage` will no longer include service bindings for a run-time image that it creates. Prior to JDK 25, `jpackage` would include service bindings for run-time images. As a result, the generated run-time images produced by `jpackage` might not include the same set of modules as it did in prior versions.
The previous behavior can be achieved with `jpackage` of JDK 25 by adding the `--bind-services` `jlink` option to the default `jlink` options `jpackage` uses:
```
jpackage [...] --jlink-options \
"--strip-native-commands --strip-debug --no-man-pages --no-header-files --bind-services"
```
The previous behavior can be achieved with `jpackage` of JDK 25 by adding the `--bind-services` `jlink` option to the default `jlink` options `jpackage` uses:
```
jpackage [...] --jlink-options \
"--strip-native-commands --strip-debug --no-man-pages --no-header-files --bind-services"
```
- backported by
-
JDK-8349738 Release Note: jpackage No Longer Includes Service Bindings by Default for Generated Run-Time Images
-
- Resolved
-