Closed toomyem closed 6 years ago
Woohoo ... that is embarrassing. No you can't. But give me a minute :grin:
the "-arch.rpm" is actually due to this bug - https://github.com/eclipse/packagedrone/issues/123
anyway, i think that it's good that you've added outputFileName (0.10.1)
it helped me workaround the issue with: <outputFileName>${project.artifactId}-${project.version}-${rpm.release}.${rpm.architecture}.rpm</outputFileName>
thank you.
I'd like to note that I also had to manually set package name in addition to outputFileName, otherwise yum wasn't able to install created rpm.
<outputFileName>${rpm.package.name}-${project.version}-1.noarch.rpm</outputFileName>
<packageName>${rpm.package.name}</packageName>
So I guess we can close this issue.
Not sure it's good to close this issue if it's not fixed. The workaround isn't perfect. I suppose that an upgrade to packagedrone, will fix that issue
@yarix You are right. I actually lost track of this being an issue in Package Drone. And there was no released yet which contained eclipse/packagedrone#126 … So I will keep this open and try to find a way to by quicker in making releases of the base RPM library.
This should be fixed in version 1.0.0 which I just released. Please re-open otherwise.
Is it possible to customize format used to create archive's name? Currently it is created with "-arch.rpm" suffix, but there is also convention to use ".arch.rpm" (with dot before arch name).