search

OpenHFT / OpenHFT

Parent module to include active modules
http://openhft.net
GNU Lesser General Public License v3.0
635 stars 180 forks source link

Referenced artifacts unavailable for Chronicle BOM 2.23.137+ #174

Open paolodedios opened 1 year ago

paolodedios commented 1 year ago

Chronicle software artifacts listed on the BOM after 2.23.136, so from 2.23.137 to 2.23.154 as of this writing, are not available on Maven central and as such I am unable to build against the latest stable releases.

Maven reports that some referenced artifacts are behind a private Nexus server:

Could not resolve dependencies for project io.appliedtheory:proof-extensions-chronicle:jar:1.0.0: 
    Failed to collect dependencies at net.openhft:chronicle-core:jar:2.23.37: 
    Failed to read artifact descriptor for net.openhft:chronicle-core:jar:2.23.37: 
    Could not transfer artifact software.chronicle:chronicle-opensource-root-pom:pom:1.0.26 from/to chronicle-enterprise-snapshots (https://nexus.chronicle.software/content/repositories/snapshots): 
    status code: 401, reason phrase: Unauthorized (401) -

Are the latest releases only available to enterprise customers? This is understandable, of course, but is there documentation or schedule as to when open source artifacts become fully available on Maven central?

alamar commented 1 year ago

Currently, the ea (latest) branch artifacts (for BOM versions such as 2.24ea40) are fully available on Maven central. Stable branch artifacts (such as for BOM version 2.23.254) are not published to Maven central.

WeatherGod commented 3 months ago

So, what is the current recommendation for those wanting to use stable branch artifacts?

tgd commented 3 months ago

Hi @WeatherGod - you can get access to stable artifacts by purchasing an enterprise license - you can reach our team via the contact form here: https://chronicle.software/contact-us/

WeatherGod commented 3 months ago

It is not up to me, as I'm only a user of an open-source project that has Chronicle-Map as a dependency. That project was waiting for a stable release to fix a bug that was found in Chronicle-Map. Now that they know that a stable release won't come (I asked about this several months ago), we can proceed in a different direction.

It would be greatly appreciated if important build/usage/distribution information was made clear in the documentation. Prior to this, I was under the assumption that the licenses were for paid support and additional features.

tgd commented 3 months ago

Hi @WeatherGod - thanks for explaining the context. I have also read through the Unidata ticket in some more detail.

Now that they know that a stable release won't come (I asked about this several months ago), we can proceed in a different direction.

We have some more documentation on exactly what EA means here: https://github.com/OpenHFT/OpenHFT/blob/ea/docs/Version-Support.adoc#ea-early-access

In our OpenHFT EA releases you get access to all work landing in develop. Can you point me towards what bug fixes in particular you are waiting for and I can investigate further.

WeatherGod commented 3 months ago

The bug fixes were already in EA and had been for months, so no need to investigate anything further. It was the developers of the Unidata project that had a policy of only using stable releases of any third-party dependencies and they were waiting for a stable release to pin in their build process. They were not aware of the change in development policy (appears to have occurred back in October?). Now that they are aware, they are moving ahead with pinning to an EA release.

peter-lawrey commented 3 months ago

Over the last few years, we have significantly enhanced the stability and quality of our releases. Our Early Access (EA) releases are now more stable than our regular releases from three years ago. We have fewer releases, and they are less likely to be followed by another release within days. All new features are introduced in the EA first.

Many of our customers opt for the EA releases to benefit from the latest updates and improvements. However, for customers seeking a fix with minimal changes from their current version, we offer a more stable, curated release. These stable releases are available on our Nexus server and are exclusive to customers with a support subscription.

Chronicle-Map is one of our more stable products anyway, but we keep the same naming convention across our products.