[
https://issues.apache.org/jira/browse/MJLINK-91?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17915981#comment-17915981
]
ASF GitHub Bot commented on MJLINK-91:
--------------------------------------
YaSuenag opened a new pull request, #242:
URL: https://github.com/apache/maven-jlink-plugin/pull/242
Following this checklist to help us incorporate your
contribution quickly and easily:
- [x] Make sure there is a [JIRA
issue](https://issues.apache.org/jira/browse/MJLINK) filed
for the change (usually before you start working on it). Trivial
changes like typos do not
require a JIRA issue. Your pull request should address just this
issue, without
pulling in other changes.
- [x] Each commit in the pull request should have a meaningful subject line
and body.
- [x] Format the pull request title like `[MJLINK-XXX] - Fixes bug in
ApproximateQuantiles`,
where you replace `MJLINK-XXX` with the appropriate JIRA issue. Best
practice
is to use the JIRA issue title in the pull request title and in the
first line of the
commit message.
- [ ] Write a pull request description that is detailed enough to
understand what the pull request does, how, and why.
- [x] Run `mvn clean verify` to make sure basic checks pass. A more
thorough check will
be performed on your pull request automatically.
- [x] You have run the integration tests successfully (`mvn -Prun-its clean
verify`).
If your pull request is about ~20 lines of code you don't need to sign an
[Individual Contributor License
Agreement](https://www.apache.org/licenses/icla.pdf) if you are unsure
please ask on the developers list.
To make clear that you license your contribution under
the [Apache License Version 2.0, January
2004](http://www.apache.org/licenses/LICENSE-2.0)
you have to acknowledge this by using the following check-box.
- [x] I hereby declare this contribution to be licenced under the [Apache
License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0)
- [ ] In any other case, please file an [Apache Individual Contributor
License Agreement](https://www.apache.org/licenses/icla.pdf).
> addOptions should concatenate arguments with "="
> ------------------------------------------------
>
> Key: MJLINK-91
> URL: https://issues.apache.org/jira/browse/MJLINK-91
> Project: Maven JLink Plugin
> Issue Type: Improvement
> Reporter: Yasumasa Suenaga
> Priority: Major
>
> JDK 25 accepts `--add-options` jlink option with `=` only due to JDK-8303884.
> See [GitHub PR on OpenJDK|https://github.com/openjdk/jdk/pull/22526] for more
> details.
> Currently Maven JLink Plugin generates jlink arguments separated by white
> space. It works fine on JDK 24 or earlier, but it will not work on JDK 25 or
> later. jlink (in JDK 24 or earlier) can be accept both style `--add-options
> <opts>` and `--add-options=<opts>`. Thus we can adopt `-add-options=` style
> for all JDK versions.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
