P3
The jlink tool should have the facility to customize the 'release' file that it generates for the custom runtime. To enhance its functionality, it should accept options to add specific details to the release file, including the original implementor, the implementor who created the runtime, the custom version, and the creation date of the custom runtime.
For instance, consider the JDK21 release file provided below:
```
IMPLEMENTOR="Oracle Corporation"
JAVA_RUNTIME_VERSION="21+35-LTS-2513"
JAVA_VERSION="21"
JAVA_VERSION_DATE="2023-09-19"
LIBC="default"
MODULES="java.base java.compiler java.datatransfer java.xml java.prefs java.desktop java.instrument java.logging java.management java.security.sasl java.naming java.rmi java.management.rmi java.net.http java.scripting java.security.jgss java.transaction.xa java.sql java.sql.rowset java.xml.crypto java.se java.smartcardio jdk.accessibility jdk.internal.jvmstat jdk.attach jdk.charsets jdk.internal.opt jdk.zipfs jdk.compiler jdk.crypto.ec jdk.crypto.cryptoki jdk.dynalink jdk.internal.ed jdk.editpad jdk.hotspot.agent jdk.httpserver jdk.incubator.vector jdk.internal.le jdk.internal.vm.ci jdk.internal.vmcompiler jdk.internal.vmcompiler.management jdk.jartool jdk.javadoc jdk.jcmd jdk.management jdk.managementagent jdk.jconsole jdk.jdeps jdk.jdwpagent jdk.jdi jdk.jfr jdk.jlink jdk.jpackage jdk.jshell jdk.jsobject jdk.jstatd jdk.localedata jdk.management.jfr jdk.naming.dns jdk.naming.rmi jdk.net jdk.nio.mapmode jdk.random jdk.sctp jdk.security.auth jdk.security.jgss jdk.unsupported jdk.unsupported.desktop jdk.xml.dom"
OS_ARCH="aarch64"
OS_NAME="Darwin"
SOURCE=".:git:a5122428f703 open:git:890adb6410da"
```
When creating a custom runtime using the provided command:
```
poonam@poonam-mac jdks % jlink --module-path $JAVA_HOME/jmods \
--add-modules java.base \
--output my-runtime
```
The resulting release file contains only basic information, such as the Java version and modules. Unfortunately, this limited information makes it impossible to determine the original implementor, who generated the custom runtime, or when it was created.
The jlink tool should be able to capture more comprehensive details in its release file, so that we can better understand who created the custom runtime and when it was created.
For instance, consider the JDK21 release file provided below:
```
IMPLEMENTOR="Oracle Corporation"
JAVA_RUNTIME_VERSION="21+35-LTS-2513"
JAVA_VERSION="21"
JAVA_VERSION_DATE="2023-09-19"
LIBC="default"
MODULES="java.base java.compiler java.datatransfer java.xml java.prefs java.desktop java.instrument java.logging java.management java.security.sasl java.naming java.rmi java.management.rmi java.net.http java.scripting java.security.jgss java.transaction.xa java.sql java.sql.rowset java.xml.crypto java.se java.smartcardio jdk.accessibility jdk.internal.jvmstat jdk.attach jdk.charsets jdk.internal.opt jdk.zipfs jdk.compiler jdk.crypto.ec jdk.crypto.cryptoki jdk.dynalink jdk.internal.ed jdk.editpad jdk.hotspot.agent jdk.httpserver jdk.incubator.vector jdk.internal.le jdk.internal.vm.ci jdk.internal.vmcompiler jdk.internal.vmcompiler.management jdk.jartool jdk.javadoc jdk.jcmd jdk.management jdk.managementagent jdk.jconsole jdk.jdeps jdk.jdwpagent jdk.jdi jdk.jfr jdk.jlink jdk.jpackage jdk.jshell jdk.jsobject jdk.jstatd jdk.localedata jdk.management.jfr jdk.naming.dns jdk.naming.rmi jdk.net jdk.nio.mapmode jdk.random jdk.sctp jdk.security.auth jdk.security.jgss jdk.unsupported jdk.unsupported.desktop jdk.xml.dom"
OS_ARCH="aarch64"
OS_NAME="Darwin"
SOURCE=".:git:a5122428f703 open:git:890adb6410da"
```
When creating a custom runtime using the provided command:
```
poonam@poonam-mac jdks % jlink --module-path $JAVA_HOME/jmods \
--add-modules java.base \
--output my-runtime
```
The resulting release file contains only basic information, such as the Java version and modules. Unfortunately, this limited information makes it impossible to determine the original implementor, who generated the custom runtime, or when it was created.
The jlink tool should be able to capture more comprehensive details in its release file, so that we can better understand who created the custom runtime and when it was created.