I don't know if this is an issue with specifically this plugin or jpackage in general, but I've found that while everything works fine on Windows 10 with MSI installers, on Fedora Linux I can't install a jpackage generated RPM normally, because it throws errors of the type file /usr/lib/.build-id/17/3f69fcb326de2e5180b4f5611157d16a5c3876 from install of my-app-name-1.1-1.x86_64 conflicts with file from package my-other-app-name-or-JDK-name-1.0-1.x86_64
This can be solved by installing from terminal with --excludeartifacts option, but it's obviously not great that having a JDK or other jpackage deployed app installed kills the option of a smooth install without a terminal and extra options.
I don't know if this is an issue with specifically this plugin or jpackage in general, but I've found that while everything works fine on Windows 10 with MSI installers, on Fedora Linux I can't install a jpackage generated RPM normally, because it throws errors of the type
file /usr/lib/.build-id/17/3f69fcb326de2e5180b4f5611157d16a5c3876 from install of my-app-name-1.1-1.x86_64 conflicts with file from package my-other-app-name-or-JDK-name-1.0-1.x86_64This can be solved by installing from terminal with --excludeartifacts option, but it's obviously not great that having a JDK or other jpackage deployed app installed kills the option of a smooth install without a terminal and extra options.Any ideas how to solve this?