jlink --include-locales has the following problems.

1) The --include-locales option doesn't support the semantics of the locale data hierarchy (tree structure). For example, if zh-Hans is specified, zh-Hans-SG is one of the selected locales, but zh-SG isn't. zh-SG is implicitly in Simplified Chinese. Another example is that if en-001 is specified, the en-* locales which have en-001 as its parent resource bundle. It's hard for users to specify language tags based on internal data hierarchy. The tool should fully take care of locale data selection.

2) List of available locales is incorrect. For example, if *-AT is specified, its available locales don't contain en-001. So, if en-AT is specified with the reduced locales, en-001 doesn't become the parent resource bundle of en-AT and its date-time format patterns are incorrect.

3) * (any language tags) doesn't work. --include-locales=* fails with ArrayIndexOutOfBoundsException. It should work as the case that --include-locales is not specified.