Adapting Talend Studio and Talend Runtime configurations after Maven Central Repository moved to HTTPS - 6.5

author
Talend Documentation Team
EnrichVersion
6.5
EnrichProdName
Talend Data Fabric
Talend Data Services Platform
Talend ESB
Talend MDM Platform
Talend Real-Time Big Data Platform
task
Deployment
EnrichPlatform
Talend ESB
Talend Runtime
Talend Studio

Adapting Talend Studio and Talend Runtime configurations after Maven Central Repository moved to HTTPS

Since January 15, 2020, the Maven Central Repository no longer supports communication over HTTP. This change requires configuration changes for users to be able to build ESB Microservices through Talend Studio and to deploy new features to Talend Runtime.

Refer to this article to get more information about the Maven Central Repository move to HTTPS.

Talend Studio

The first time you try to build ESB Microservices, Talend Studio tries to fetch some artifacts from the Maven Central Repository. This automatic step will fail for existing installations of Talend Studio as the default configuration relies on HTTP.

Adapt the default configuration as follows:

  1. Add the following lines, from <mirrors to </mirrors> to the <studio_path>/configuration/maven_user_settings.xml configuration file.
    <?xml version="1.0" encoding="UTF-8"?>
    <settings xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.1.0 http://maven.apache.org/xsd/settings-1.1.0.xsd" xmlns="http://maven.apache.org/SETTINGS/1.1.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
        <localRepository>....</localRepository>
    	<!-- add these lines -->
    	<mirrors>
    		<mirror>
    			<id>official</id>
    			<name>repo.maven.apache.org</name>
    			<url>https://repo.maven.apache.org/maven2</url>
    			<mirrorOf>central</mirrorOf>
    		</mirror>
    	</mirrors>
    	<!-- end -->
    </settings>
  2. In Talend Studio, go to Preferences > Maven and make sure that the Offline option is unchecked. Talend Studio needs to have Maven set to online mode to make use of the mirror settings added previously.

You should now be able to create ESB Microservices again.

Talend Runtime

Deploying features to Talend Runtime can also require a Maven Central Repository access. By default, Talend Runtime is set to communicate over HTTP.

Adapt the default configuration as follows:

  1. Set the Maven Central Repository URL to HTTPS in the <Talend_Runtime_path/etc/org.ops4j.pax.url.mvn.cfg configuration file. Update the org.ops4j.pax.url.mvn.repositories parameter to https://repo1.maven.org/maven2@id=central.

You should now be able to deploy features to Talend Runtime again.