Four Stars

Talend Artifact Repository vs Nexus Repository OSS

Hi there,

Our team is looking to use Nexus Repository to store and manage artifacts not just for Talend, but for various other projects.

 

So, for Talend to work as advertised, is it required that we install Artifact Repository included in the Talend installer or can we use Nexus Repository (https://www.sonatype.com/nexus-repository-oss) that's not part of the Talend installer? Will there be issues when publishing artifacts from Talend Studio when we use a non-Talend sanctioned Nexus instance?

 

Thank you. 

  • Talend Repository Manager
1 ACCEPTED SOLUTION

Accepted Solutions
Employee

Re: Talend Artifact Repository vs Nexus Repository OSS

You can use Nexus Repository OSS as long as it is the version specified in our documentation.  For example, this url https://help.talend.com/#/reader/15alggfW5LpDeQ2mZKiokg/oxYJr9_vG6VgjP3DcWPg7w says Sonatype Nexus 2.11.  Search https://help.talend.com for the installation documentation for your version of the Talend product you have and check the Nexus version recommended there.

 

Only the version listed in the Talend installation guide is compatible with the product suite.  You should also create the repositories that talend pre-package in your Nexus instance.  You can compare the Talend pre-packaged Nexus with yours, and create all the repositories needed.

 

Other than the pre-defined Talend repositories for software updates and thirdparty libraries, the Nexus provided by Talend is pretty much vanilla.  

 

If you encounter an issue, you will be required to reproduce the issue with a Nexus repository provided by Talend first, to make sure you have not missed any configuration provided by the packaged Nexus in the Talend installer.

 

Note:  Talend does not support Nexus 3.x yet due to some API changes in the 3.x Nexus.  So you need to stay on the version that Talend has.

 

Another way that is possible:

1) Use the Talend Nexus for Talend work

2) Use your central Nexus repository for other work and projects to proxy the Talend Nexus repositories.  This way from a management perspective, they do appear in 1 nexus, just leveraging Nexus proxy feature.  

 

If you have the paid version of Nexus, you can even leverage the Smart Proxy feature in Nexus.

1 REPLY
Employee

Re: Talend Artifact Repository vs Nexus Repository OSS

You can use Nexus Repository OSS as long as it is the version specified in our documentation.  For example, this url https://help.talend.com/#/reader/15alggfW5LpDeQ2mZKiokg/oxYJr9_vG6VgjP3DcWPg7w says Sonatype Nexus 2.11.  Search https://help.talend.com for the installation documentation for your version of the Talend product you have and check the Nexus version recommended there.

 

Only the version listed in the Talend installation guide is compatible with the product suite.  You should also create the repositories that talend pre-package in your Nexus instance.  You can compare the Talend pre-packaged Nexus with yours, and create all the repositories needed.

 

Other than the pre-defined Talend repositories for software updates and thirdparty libraries, the Nexus provided by Talend is pretty much vanilla.  

 

If you encounter an issue, you will be required to reproduce the issue with a Nexus repository provided by Talend first, to make sure you have not missed any configuration provided by the packaged Nexus in the Talend installer.

 

Note:  Talend does not support Nexus 3.x yet due to some API changes in the 3.x Nexus.  So you need to stay on the version that Talend has.

 

Another way that is possible:

1) Use the Talend Nexus for Talend work

2) Use your central Nexus repository for other work and projects to proxy the Talend Nexus repositories.  This way from a management perspective, they do appear in 1 nexus, just leveraging Nexus proxy feature.  

 

If you have the paid version of Nexus, you can even leverage the Smart Proxy feature in Nexus.