Introduction
This article contains some information and steps that should be performed due to the switch of Intershop Public Repository Server to SaaS solution. It also contains examples of how to use Sonatype Nexus.
References
New Intershop Public Repositories
Maven and Ivy repositories have been moved from https://repository.intershop.de to SaaS solution at https://repository.cloud.intershop.com effective October 25. The old repository at https://repository.intershop.de will be shut down on November 1. The new credentials (username and password) for new Intershop Maven- or Ivy-repositories are available on the Repository Contract Page in the Support Portal (https://support.intershop.com/sws/index.php?c=ContractView&q1=Repo).
According to our documentation (Cookbook - Setup CI Infrastructure) the use of a proxy cache like Sonatype Nexus becomes necessary. Intershop automatically monitors the number of downloads and requests and reserves the right to restrict access to artifacts if no proxy is set up.
If a proxy cache is not in place already, then please set it up as soon as possible. It is not necessary to remove or replace the old existing Intershop Repository due to the reuse of already cached artifacts.
Below are some steps and basics that are helpful for configuring new Intershop Public Repositories.
Proxy Caching
The caching of artifacts is ensured by an Artifact Repository Server via proxy repositories. This should be done for the repositories JCenter, Central and especially for Intershop Public Repositories.
In addition, the Main Artifact Repository must be used as a proxy in case there are other Artifact Repository Servers that need to access artifacts from Intershop Public Repositories. This could be the case in local development or test environment where, for example, a local Nexus is used.
Repository Data
Below is the list of required proxy repositories with the new Intershop Public Repository URLs.
| Name | ID | Repository Type | Previous Remote Storage Location | New Remote Storage Location | Format | Remarks |
|---|---|---|---|---|---|---|
| JCenter | jcenter | Proxy | https://jcenter.bintray.com/ | https://jcenter.bintray.com/ | Maven2 | No changes required |
| Central | central | Proxy | https://repo1.maven.org/maven2/ | https://repo1.maven.org/maven2/ | Maven2 | |
| Intershop | ishrepo | Proxy | https://repository.intershop.de/releases | https://repository.cloud.intershop.com/releases/ | Maven2 | Changes required |
| Intershop Ivy | ivy-intershop | Proxy | https://repository.intershop.de/ivy-releases | https://repository.cloud.intershop.com/ivy-releases/ | Ivy | Changes required Included in Intershop Releases Repository (ishrepo) |
| Intershop Maven | mvn-intershop | Proxy | https://repository.intershop.de/mvn-releases | https://repository.cloud.intershop.com/mvn-releases/ | Maven2 |
The username and password for new Intershop Maven- and Ivy-repositories are available in the "Repository" tab in the Contract context via Support Portal.
URL: https://support.intershop.com/sws/index.php?c=ContractView&q1=Repo
Add New Proxy Repository for Intershop Artifacts
This part describes how to set up the new Intershop Releases Proxy Repository on the Main Artifact Repository Server using Sonatype Nexus as an example.
Step 1: Add a new Proxy Repository for the Public Intershop Repository.
Switch to the Routing tab and make sure Discovery is unchecked.
Step 2: Add New Intershop Proxy Repository to the Components Group.
Configure a Proxy Repository to the Main Artifact Repository Server
This part describes how to set up a proxy repository on a different Artifact Repository Server so that the Intershop artifacts are pulled from the Main Artifact Repository.
This will also fill the Main Artifact Repository server with artifacts that have not yet been downloaded.
Step 1: Copy Intershop Proxy Repository URL from Main Artifact Repository Server.
Step 2: Add new Proxy Repository to the other Artifact Repository Server to use already downloaded Artifacts from the Main Artifact Repository Server.
Step 3: Add the new Proxy Repository to the Components Group.
