JDK-8187897 : For ant-java.jar, should accept only new arguments
- Type: Sub-task
- Component: deploy
- Sub-Component: packager
- Priority: P3
- Status: Resolved
- Resolution: Delivered
- Submitted: 2017-09-25
- Updated: 2017-10-26
- Resolved: 2017-10-26
The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
| JDK 10 |
|---|
10Resolved  |
Description
Currently we use internal arg ids for specifying bundleArguments.
For example,
<fx:bundleArgument arg="mainJar" value="hello.world.jar"/>
<fx:bundleArgument arg="win.exe.systemWide" value="true"/>
<fx:bundleArgument arg="signBundle" value="true"/>
We shouldn't allow users to use internal argument ids. Instead, they will need to use new arguments ids (without "--"), like this:
<packager:bundleArgument arg="main-jar" value="hello.world.jar"/>
<packager:bundleArgument arg="system-wide" value="true"/>
<packager:bundleArgument arg="sign" value="true"/>
In case the value specified for "arg" is not new arg id, we need to show a warning and ignore it.