Customizing the Maven URI for external module deployment
In Talend Studio, each external module is given a default URI to identify its deployment in Maven. You can use a specific version of an external module by providing its Maven URI as a custom Maven URI. This will cause the builder to download and use the Jar file specified by the Custom Maven URI instead.
For example, you can use a specific version of a database driver by providing the Maven URI of the database driver, given that the corresponding external module is available.
- Changing the Maven URI for an external module will affect all the components and metadata connections that use the module within the project.
- A customized Maven URI applies to the current project only.
- Customized Maven URIs apply to the current branch only.
- Customized Maven URIs are stored in {your-studio-installation-path}/workspace/{your-project}/.settings/custom_uri_mapping.json.
- When working on a remote project, your custom Maven URI settings will be automatically synchronized to the GIT Repository and will be used when other users working on the same project. CI Builder will also use this when generating the POM files.
Procedure
-
If you want to install another version of the external module, specify
the full path to the module file in the Module File
field, or click the [...] button to browse in your
local file system.
If you have installed the R2020-10 Studio monthly update or a later one provided by Talend, and if the MVN URI of the library is within the jar file and is different from the default MVN URI, it is automatically detected and filled in the Custom MVN URI field.
