oVirt artifacts at maven repository

Alon Bar-Lev alonbl at redhat.com
Thu Nov 22 07:15:16 UTC 2012


Hello,

The otpoi and ovirt-host-deploy projects provides java artifacts so that ovirt-engine can be built using common constants and trivial parser.

I would like to publish these artifacts at maven central to ease ovirt-engine build, as it will automatically fetch these dependencies just like every other dependency.

In order to do so I need to sign the artifacts.

Questions:

Should we have unique key for each package?
Should we have single key for all oVirt releases?

The advantages of a key for each package is that the maintainer can release artifacts at will.
The advantage of single key is that a single trust can be obtained.

What do you think?
Alon.



More information about the Arch mailing list