JDK-8229138 : Add --linux-app-release option for DEB and RPM packages
  • Type: Bug
  • Component: tools
  • Sub-Component: jpackage
  • Affected Version: internal
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • OS: linux
  • CPU: x86_64
  • Submitted: 2019-08-05
  • Updated: 2019-08-27
  • Resolved: 2019-08-14
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.
Other
internalFixed
Related Reports
Cloners :  
JDK-8213941 - Debian linux problems in JavaPackager
Relates :  
JDK-8228660 - .deb files generated by jpackage don't follow naming convention
Description
These problems were reported against the packager that Johan Vos backported for OpenJDK 11.

The jpackager command line should have the flag --release in addition to
--version. The only way to set a different release than "1" is to supply a
custom spec file for RPM and control file for DEB.
package/linux/test.spec
Version: 1.0.0
Release: RC1
package/linux/control
Version: 1.0.0-RC1

Need to add cli option "--linux-app-release <value>" to satisfy the request.
Comments
currently, the hardwired release value is "1", so I have made the default value of --linux-app-release "1". would "ea" or "unknown" be a better default value ?
13-08-2019
webrev: http://cr.openjdk.java.net/~herrick/8229138/webrev.01/
13-08-2019