Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

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

Closed
jbellis opened this issue Apr 21, 2024 · 2 comments
Closed

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

jbellis opened this issue Apr 21, 2024 · 2 comments
Labels
wontfix

Comments

@jbellis
Copy link

jbellis commented Apr 21, 2024

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
Copy link
Contributor

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

@JerryShea JerryShea closed this as not planned Won't fix, can't repro, duplicate, stale Apr 22, 2024
@jbellis
Copy link
Author

jbellis commented Apr 22, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
wontfix
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jbellis @JerryShea