Feedback from Sverre Moe <sverre.moe@gmail.com>:
When using a control file from the resource directory, jpackage does not
use its version and release.
Must apply "--app-version" and "--linux-app-release" in order to get the
proper version and release on file name.
Running dpkg-deb --show and --info has the correct version and release.
dpkg-deb --show build/deb/application_1.0-1_amd64.deb
application 1.1.0-SNAPSHOT20190904113134
I wonder where it gets the version 1.0 from, since my
project.version=1.1.0. The jpackage should at least use the project version
if no other version is specified.
This is a problem only for the debian package on Linux. When building an
RPM, jpackage uses both the Version and Release defined within the spec
resource file.
When using a control file from the resource directory, jpackage does not
use its version and release.
Must apply "--app-version" and "--linux-app-release" in order to get the
proper version and release on file name.
Running dpkg-deb --show and --info has the correct version and release.
dpkg-deb --show build/deb/application_1.0-1_amd64.deb
application 1.1.0-SNAPSHOT20190904113134
I wonder where it gets the version 1.0 from, since my
project.version=1.1.0. The jpackage should at least use the project version
if no other version is specified.
This is a problem only for the debian package on Linux. When building an
RPM, jpackage uses both the Version and Release defined within the spec
resource file.
- relates to
-
JDK-8233143 RPM errors: rpmbuild: no spec files given for build
-
- Resolved
-