As https://github.com/jetty-project/jetty-alpn/issues/22 shows, the OpenJDK patch version can't always reliably be used to determine which alpn boot version should be used, due to distributions backporting security fixes to patch versions rather than updating to the latest patch version. It's likely infeasible to correctly map every distributions possible version string correctly, so as an escape hatch, it would help if the agent supported an argument to override the detection, and force a particular alpn boot version to be used.
As https://github.com/jetty-project/jetty-alpn/issues/22 shows, the OpenJDK patch version can't always reliably be used to determine which alpn boot version should be used, due to distributions backporting security fixes to patch versions rather than updating to the latest patch version. It's likely infeasible to correctly map every distributions possible version string correctly, so as an escape hatch, it would help if the agent supported an argument to override the detection, and force a particular alpn boot version to be used.