Blog ›Hazelcast Maven Repository URL Change

By Jiri Holusa

Product Manager, Platform

Jiri is a devoted open source software engineer that loves his work. Born in Red Hat and later Hazelcast as a Quality Engineer, he is now the Product Manager of Hazelcast IMDG. Digging deep and never giving up on a problem until it’s solved and enjoying this all the way, that’s Jiri. Besides that, he loves basically any sport and as a true Czech person, he never refuses a pleasant conversation over a pint of beer.

View all blogs by the author

Jan 29, 2019

Back to Blog

Hazelcast Maven Repository URL Change

We are announcing a change to Hazelcast’s Maven repository URL from repository-hazelcast-l337.forge.cloudbees.com (old) to repository.hazelcast.com (new). This change is due to the end-of-life of our current infrastructure effective 31st January 2019. After that, the old Maven repository becomes unavailable.

Who is affected?

The change affects only customers of Hazelcast Enterprise downloading the builds via Maven repository. Customers who downloaded the builds via our website (e.g., ZIP or TAR files) are not affected. Users of Hazelcast Open Source are not affected at all.

Solution

We migrated the whole Maven repository to a new place. The only action users must take is to update the URL of the Maven repository to:repository.hazelcast.com. To be specific, user has to change in the dependency management (e.g. Maven pom.xml) this section:

Old URL:

<repository>
    <id>Hazelcast Private Snapshot Repository</id>
    <url>https://repository-hazelcast-l337.forge.cloudbees.com/snapshot/</url>
</repository>
<repository>
    <id>Hazelcast Private Release Repository</id>
    <url>https://repository-hazelcast-l337.forge.cloudbees.com/release/</url>
</repository>

New URL:

<repository>
    <id>Hazelcast Private Snapshot Repository</id>
    <url>https://repository.hazelcast.com/snapshot/</url>
</repository>
<repository>
    <id>Hazelcast Private Release Repository</id>
    <url>https://repository.hazelcast.com/release/</url>
</repository>

To summarize, the only change needed is to substitute “repository-hazelcast-l337.forge.cloudbees.com” with “repository.hazelcast.com” in the dependency management system configuration.

We hope that this change won’t cause any inconveniences and thank you for your understanding.