On Thu, 20 Nov 2025 10:33:32 GMT, Jaikiran Pai <[email protected]> wrote:
> Correct, but not necessarily UTF-8. It expects the input file to be UTF-8 now. So I've added that the plugin help text in https://github.com/openjdk/jdk/pull/28399/commits/2f48c81b90e358dabd01b96a89e2dcc9d882c781 > I am not familiar where all this release-info gets used during jlink and then > in the generated image. It's the plugin that creates the `$JDK/release` file. That's it. > So whatever encoding is appropriate for such content, I think we should > specify it, in the help text and man page of jlink. I've added it to the `--list-plugin` help text now. Plugins aren't mentioned in the `jlink` man page, so it doesn't seem appropriate to mention it the `jlink` man page. Here is how it looks like when using `jlink --list-plugins` with the latest update: --release-info <file>|add:<key1>=<value1>:<key2>=<value2>:...|del:<key list> <file> option is to load release properties from the supplied file. The specified file is expected to be encoded in UTF-8. add: is to add properties to the release file. Any number of <key>=<value> pairs can be passed. del: is to delete the list of keys in release file. ------------- PR Comment: https://git.openjdk.org/jdk/pull/28399#issuecomment-3557356452
