DependencyResolutionException errors from epdev offline maven
Article ID: KB0074804
Updated On:
| Products | Versions |
|---|---|
| TIBCO Streaming | 10 |
Description
How can we fix errors like this reported from running 'epdev offline maven'?
Getting artifacts for simple-eventflow-fragment-20 in str-10.5.1-SNAPSHOT-product-artifacts-repo-offline-projects.zip. [ERROR] Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:3.1.2:go-offline (default-cli) on project simple-eventflow-fragment-20: org.eclipse.aether.resolution.DependencyResolutionException: The following artifacts could not be resolved: com.tibco.ftl:tibftl:jar:6.0.1, com.tibco.ftl:group:jar:6.0.1: Could not find artifact com.tibco.ftl:tibftl:jar:6.0.1 in central (https://repo.maven.apache.org/maven2) -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException .Maven exit 1 for -T2 org.apache.maven.plugins:maven-dependency-plugin:3.1.2:go-offline -f /tmp/offline3429405480130364339/ 0/simple-eventflow-fragment-20/pom.xml -Dcom.tibco.ep.ep-maven.product=/tmp/offline3429405480130364339/product-install
Issue/Introduction
Installation guidance
Resolution
In most cases these errors do not indicate a problem since the libraries affected are optional and not related to core functionality.
After disconnecting from the internet, it is best practice to create a new StreamBase project in Studio and confirm that the new project is created, then load a sample project and confirm it can build and run. If these two tests pass, then Studio is likely fully set-up for offline use.
As of the 10.6.0 release, the list of optional libraries which may need to be supplied separately for specific projects are:
This list will change in future releases. For most projects 'epdev' errors related to these libraries may be ignored.
If you find your project requires any of these libraries, make sure that you:
1. Install the optional TIBCO-provided installers (for example, the installer for the StreamBase High-Performance FIX Engine), and then re-run 'epdev offline maven'.
2. Install any additional TIBCO products needed for your project and obtain the libraries from those installs.
3. Obtain these libraries from their non-TIBCO manufacturers.
Additional libraries may be individually installed into your Maven Repository using the instructions from TIBCO Streaming documentation page:
TIBCO Streaming > Authoring Guide > StreamBase Projects and Files > Using External JAR Files
After disconnecting from the internet, it is best practice to create a new StreamBase project in Studio and confirm that the new project is created, then load a sample project and confirm it can build and run. If these two tests pass, then Studio is likely fully set-up for offline use.
As of the 10.6.0 release, the list of optional libraries which may need to be supplied separately for specific projects are:
com.db:abfx-apiConfig:jar:1.4 com.db:abfx-compatible-command:jar:1.4 com.db:abfx-compatible-commandtransport:jar:1.4 com.db:abfx-compatible-domain:jar:1.4 com.db:abfx-compatible-messaging:jar:1.4 com.db:abfx-compatible-ratesapi:jar:1.4 com.db:abfx-compatible-services:jar:1.4 com.db:abfx-compatible-utils:jar:1.4 com.db:abfx-fwdcommon:jar:1.4 com.db:abfx-fwdpricing:jar:1.4 com.db:abfx-fxpricinglib:jar:1.4 com.db:abfx-indexpricing:jar:1.4 com.db:abfx-ratesapi:jar:1.4 com.db:abfx-utils:jar:1.4 com.db:nClient:jar:1.0 com.db:nmessaging:jar:1.0: com.epam:fast-adaptor-api:jar:2.14.25 com.epam:fast-bovespafastadaptor-api:jar:2.14.25 com.epam:fast-bovespafastadaptor-bean:jar:2.14.25 com.epam:fast-bovespafastadaptor-core:jar:2.14.25 com.epam:fast-bovespafastadaptor-tags:jar:2.14.25 com.epam:fast-bovespafastadaptor-transport:jar:2.14.25 com.epam:fast-cme-xmlbeans:jar:2.14.25 com.epam:fast-engine-small:jar:2.14.25 com.epam:fixaj-adaptor:jar:2.21.0 com.epam:fixaj-cmeilinkadaptor:jar:2.21.0 com.epam:fixaj-engine-all:jar:2.21.0 com.epam:fixprotocol-fix:jar:1.5.54 com.epam:pgputil-common:jar:1.1.2: com.exegy:XCAPI:jar:3.5.0 com.ibm:com.ibm.mq.commonservices:jar:7.1.0.3 com.ibm:com.ibm.mq.headers:jar:7.1.0.3 com.ibm:com.ibm.mq.jmqi:jar:7.1.0.3 com.ibm:com.ibm.mq.pcf:jar:7.1.0.3 com.ibm:com.ibm.mq:jar:7.1.0.3 com.microsoft:sqljdbc4:jar:4.0.2206.100: com.oracle:ojdbc6_g:jar:11.2.0.3.0 com.tibco.eftl:tibeftl:jar:3.4.0 com.tibco.ftl:group:jar:6.0.1: com.tibco.ftl:tibftl:jar:6.0.1 com.wombat:mamajni3:jar:3.3.18 com.wombat:mamajni4:jar:4.0.13h com.wombat:mamajni5:jar:5.0.6j javax.resource:connector:jar:1.0
This list will change in future releases. For most projects 'epdev' errors related to these libraries may be ignored.
If you find your project requires any of these libraries, make sure that you:
1. Install the optional TIBCO-provided installers (for example, the installer for the StreamBase High-Performance FIX Engine), and then re-run 'epdev offline maven'.
2. Install any additional TIBCO products needed for your project and obtain the libraries from those installs.
3. Obtain these libraries from their non-TIBCO manufacturers.
Additional libraries may be individually installed into your Maven Repository using the instructions from TIBCO Streaming documentation page:
TIBCO Streaming > Authoring Guide > StreamBase Projects and Files > Using External JAR Files
Feedback
Yes
No
Powered by
