Hi Enrico,
For now we’re not publishing to Maven Central, but I agree that it would be ideal.
Currently,
we publish to JFrog, which I think is not too hard to add to a project so they can start depending on our artifacts, but it is non-standard compared to Maven Central.
IIUC, one of the hurdles to publishing to Maven Central is that we need to have all of our dependencies be present on Maven Central as well, which I believe is not the case today. If that is true, then the path to getting on Maven Central would entail:
1. Identifying all dependencies that are not on Maven Central.
2. For each one, decide whether to work with the maintainer to get those onto Maven Central, or else swap for an equivalent dependency that is available on Maven Central.
3. Do whatever remaining legwork is still missing after that for Venice artifacts to land on central.