On 01-06-2021 15:59, Florian Weimer wrote:
* Peter Boy:
>
https://docs.fedoraproject.org/en-US/packaging-guidelines/Java/#_pre_buil...
>
> therein the following passus:
>
> == JAR file installation ==
> The following applies to all JAR files except JNI-using JAR files and
application-specific JAR files (i.e., JAR files that can only reasonably be used as part
of an application and therefore constitute application-private data).
> === Split JAR files ===
> If a project offers the choice of packaging it as a single monolithic JAR or several
ones, the split packaging SHOULD be preferred.
>
>
> seems to be the problem.
The splitting is all about what you need at the end of
the day. Take
https://github.com/hibernate/hibernate-orm/ as an example. WildFly
doesn't need everything so it makes sense to split Hibernate ORM into
different RPMs (or not produce RPMs for certain jars).
WildFly can be split in similar vain, however I would choose a higher
granularity and take as much as you can into a single RPM to start with.
Does Wildfly offer any packaging choices at all?
Yes, you can focus on a subset like the servlet distribution.
https://github.com/wildfly/wildfly/blob/master/servlet-feature-pack/galle...
Probably then going for additional individual extensions to build up to
what amounts to the full distribution.
And it seems that the issue blocking Wildfly is actually *building*
stuff from source, so the delivery mechanism doesn't matter, I think.
Thanks,
Florian
I'm not sure what you mean by this. Could you elaborate?
Carlo