versions referenced by BOM don't actually exist in maven central

OpenHFT / Chronicle-Map

Replicate your Key Value Store across your network, with consistency, persistance and performance.

http://chronicle.software/products/chronicle-map/

Apache License 2.0

2.73k stars 467 forks source link

versions referenced by BOM don't actually exist in maven central #537

Closed jbellis closed 2 months ago

jbellis commented 2 months ago

Example: https://mvnrepository.com/artifact/net.openhft/chronicle-bom/2.24.99 references core version 2.24.31

which does not exist at https://mvnrepository.com/artifact/net.openhft/chronicle-core

JerryShea commented 2 months ago

hi @jbellis - this is by design - see https://github.com/OpenHFT/OpenHFT/blob/ea/docs/Version-Support.adoc#ea-early-access

Only the latest ea versions are deployed to maven central

jbellis commented 2 months ago

I see. Does that actually create material revenue opportunities? I have to imagine that most people would just build it from source. So mostly this just increases the adoption difficulty.