On 01-06-2021 08:38, Peter Boy wrote:
> Am 01.06.2021 um 02:22 schrieb Adam Young
> Why is an RPM not feasible?
I don’t know all the details. Please correct me if my knowledge is incomplete or
incorrect. But as to my knowledge, according to Fedora packaging policy the source code
must be completely compiled on Fedora infrastructure and each library must become a
separate package. For very large and complex Java programs like Wildfly, this is an
enormous amount of work and also fits poorly with the Java build system. In this respect,
building a rpm is theoretically possible, but practically not feasible with the available
resources. There was an attempt a few years ago, but it was not completed as to my
Yes, the packaging guidelines are pretty strict.
It was completed up to the point of a working Web Profile with some
extensions. See https://fedoraproject.org/wiki/Features/JBossAS7
To give an indication of the amount of dependencies that would need to
be packaged you can look at
Nowadays we acknowledge 277 components in EAP 7.4 (which is based on
The most important thing to understand is Fedora uses Xmvn to build
Maven projects, not Apache Maven. In a very small nutshell it boils down
to GAVs in poms being ignored and only (RPM) installed GAs are used.
If there is something wrong with this argument, please correct or add to it. This would
be important for the attempt of a simple Wildfly installation.