On Tue, Oct 5, 2021 at 10:20 PM Peter Boy <pboy(a)uni-bremen.de> wrote:
> Am 04.10.2021 um 21:08 schrieb Fabio Valentini <decathorpe(a)gmail.com>:
>
>
> But then you're back to *exactly how Fedora packages for Java projects
> already work* - only with the added complication that distributing
> those build artifacts as plain JARs instead of RPMs now makes them
> impossible to consume as dependencies from other RPM builds.
I think, the key is "via a Fedora managed repository“, something like a
fedora.maven.central. That could make the process easier.
Somewhere I had read on "federated ....repository“ as a specific narrow defined
cooperation with distributions or projects with similar principles as Fedora.
Yes, also distributing jars via maven is a lot simpler than having to
package them (even if just wrapped) as RPM, so there's a lot of saving
just by that.
Those jars could be rebuilt from source, including their transitive
deps, or just a mirror of maven central if we trust the upstream (and
in many cases we do, i.e. for things coming from
Eclipse.org or
Apache).
The infrastructure, I can't hardly think of this as an additional
burden, we have already hosted and built every single distribution
since the beginning of time, including those same jars in an RPM form.
Cheers,
Mario
--
Mario Torre
Manager, Software Engineering, core OpenJDK
Red Hat GmbH <
https://www.redhat.com>
9704 A60C B4BE A8B8 0F30 9205 5D7E 4952 3F65 7898