Maven build errors "dependencies could not be resolved" and "failure to transfer"
Article ID: KB0078125
Updated On:
| Products | Versions |
|---|---|
| TIBCO Streaming | - |
Description
I am using TIBCO Streaming and tried to update my projects from an earlier version. How can I resolve these errors?
Errors:
Errors:
maven-compiler-plugin:3.8.0 or one of its dependencies could not be resolved
Failure to transfer org.apache.maven.plugins:maven-resources-plugin:pom:3.1.0 from https://repo.maven.apache.org
Issue/Introduction
Configuration guidance
Resolution
When upgrading to a new version of TIBCO Streaming, many library versions change to more recent releases in order to improve the platform. Each new library version needs to be loaded into your local Maven repository. By default, the maven-compiler-plugin in Studio tries to download the new library versions from the known repositories. The default repository is:
https://repo.maven.apache.org
also known as "Maven Central".
These errors occur because the system on which StreamBase Studio is running does not have network access to any repository which has the required version of the library, including Maven Central.
As a test you may use a browser to go to:
https://repo.maven.apache.org
and see if that works from a web browser. If not, please allow outbound network connections to the Internet on this system. If you cannot, then you will need to add a maven "settings.xml" file to redirect requests to different repository which is valid on your network. The syntax for this is (for example):
https://maven.apache.org/guides/mini/guide-mirror-settings.html
Another source of these errors is if after a failure to download a needed library version, maven has added placeholder files with the file-extension ".lastUpdated" into your local repository. These can prevent new downloads for a time (usually one day).
Check in your local .m2/repository for the missing library. In the example errors above look for:
org/apache/maven/plugins/maven-resources-plugin/3.1.0
org/apache/maven/plugins/maven-compiler-plugin/3.8.0
If these exist but the pom,xml or the library .jar have an appended .lastUpdated extension, then these artifacts are unavailable to the build. You may attempt to perform a mvn install -U command from the command-line in your project directory (the same directory that the pom.xml file is in) which will force an update of the missing artifacts (from your other available repositories). If this doesn't work, you can find and remove all the files with the .lastUpdated file extension and try to perform a normal build:
Linux: find -name \*.lastUpdated -exec rm -fv {} +
Windows PowerShell: ls *.lastupdated -Recurse | rm
After there are no .lastUpdated files and network access to Maven Central (or a mirror) is available, then the needed libraries should download to support the build and these errors will not reoccur.
https://repo.maven.apache.org
also known as "Maven Central".
These errors occur because the system on which StreamBase Studio is running does not have network access to any repository which has the required version of the library, including Maven Central.
As a test you may use a browser to go to:
https://repo.maven.apache.org
and see if that works from a web browser. If not, please allow outbound network connections to the Internet on this system. If you cannot, then you will need to add a maven "settings.xml" file to redirect requests to different repository which is valid on your network. The syntax for this is (for example):
<settings>
<mirrors>
<mirror>
<id>UK</id>
<name>UK Central</name>
<url>http://uk.maven.org/maven2</url>
<mirrorOf>central</mirrorOf>
</mirror>
</mirrors>
</settings>
as described here:https://maven.apache.org/guides/mini/guide-mirror-settings.html
Another source of these errors is if after a failure to download a needed library version, maven has added placeholder files with the file-extension ".lastUpdated" into your local repository. These can prevent new downloads for a time (usually one day).
Check in your local .m2/repository for the missing library. In the example errors above look for:
org/apache/maven/plugins/maven-resources-plugin/3.1.0
org/apache/maven/plugins/maven-compiler-plugin/3.8.0
If these exist but the pom,xml or the library .jar have an appended .lastUpdated extension, then these artifacts are unavailable to the build. You may attempt to perform a mvn install -U command from the command-line in your project directory (the same directory that the pom.xml file is in) which will force an update of the missing artifacts (from your other available repositories). If this doesn't work, you can find and remove all the files with the .lastUpdated file extension and try to perform a normal build:
Linux: find -name \*.lastUpdated -exec rm -fv {} +
Windows PowerShell: ls *.lastupdated -Recurse | rm
After there are no .lastUpdated files and network access to Maven Central (or a mirror) is available, then the needed libraries should download to support the build and these errors will not reoccur.
Feedback
Yes
No
Powered by
