CICD build fails with the message Could not resolve dependencies for project. An example of this error message in the Maven build log is shown below:
Caused by: org.apache.maven.project.DependencyResolutionException: Could not resolve dependencies for project org.example.talend731_os21apr.code:routines:jar:7.3.1: The following artifacts could not be resolved: org.talend.components.lib:talend_file_enhanced:jar:1.1, org.talend.libraries:org.talend.dataquality.parser:jar:7.3.1, org.talend.daikon:crypto-utils:jar:0.31.12: Could not find artifact org.talend.components.lib:talend_file_enhanced:jar:1.1 in <Repository Name> (https://Repository.url:443/)
Cause
There are two potential causes:
- Cause 1
- org.talend.components.lib:talend_file_enhanced:jar:1.1 is missing from the listed repository in the /org/talend/components/lib/talend_file_enhanced/1.1 folder.
- Note: If there is a JAR file name appended with is last updated, this is a false positive and the real JAR file is not present.
- Cause 2
- org.talend.components.lib:talend_file_enhanced:jar:1.1 is missing from one of the listed repositories. However, further logs in the build may show that the JAR file is in the backup location if numerous repositories are set up in the maven_settings.xml file.
Solution
You can find the dependent JAR file in the local .m2 repository of the
studio/tac folder used for your development project. For example:
<Studio_Home>/Studio/configuration/.m2/repository/org/talend/components/lib/talend_file_enhanced/1.1/.
If this does not work, you can also try:
- Check the local studio/TAC .m2 repository.
- Get the JAR file from the Maven Central Repository.
- Contact the developer who built the project (for custom JARs).
Environment
