Release Date: October, 17th 2017
On This Page
Overview
- Talon 3.7.253 (The core X runtime) - [Release Notes] [Manual] [javadoc]
- Hornet 1.7.2 (Topic Oriented Application Framework) - [Release Notes] [source] [javadoc]
- Native Runtime 3.7.44
- Perf 3.7.253
- Solace Binding 3.7.253 - [javadoc]
- JMS Binding 3.7.253
- Eagle 2.3.4 (Service Framework) [Release Notes]
- Robin 2.4.2 (Deployment Orchestration) - [Release Notes]
- Samples 3.7.2 - [source]
- Apps 2.7.2 -[source]
This is a patch release of 3.7. It contains bug fixes and improvements in Eagle. Otherwise the other component versions remain unchanged from the last 3.7 Release.
Downloads
You need a login and license for the following direct downloads. Visit http://license.neeveresearch.com to request an evaluation license or contact sales@neeveresearch.com.
If you are a Maven user, see the section below for maven dependency information.
- Talon Distributions [Linux x86-64] [Win x86-64] [OSX x86-64]
- Hornet [jar]
- Robin Distributions [Linux x86-64] [Win x86-64] [OSX x86-64]
- Robin Jar [jar]
Maven
Bill of Materials
You can add the following to your pom's dependency management section to specify the versions of the artifacts for this relate. Note that this mechanism does not specify maven plugin versions.
Platform Maven Plugin
The maven BOM mechanism doesn't cover plugin versions. Consequently, the platform provides a platform plugin that incorporates the plugin goals of other plugins in the product suite. This allows specification of bom version as a property that can also be used to configure the plugin version.
Repository Configuration
Components of the platform requiring a X Platform license are stored in our licensed repositories. You can specify the repository credentials provided to you by our license server by editing your ~/.m2/settings.xml
If your project uses maven you can use the following repository targets to pick up platform dependencies:
Blocked By a Firewall?
If access to our repositories is blocked by a firewall execute the following steps to install the X jars in your Maven repository
Installing X Jars into your Local Maven Repository
- Download the X distribution using one of the following links depending on the platform for which jars need to be installed into your Maven repository
- Un-archive the distribution and execute the following command from the root of the extracted bundle:
- For win-x86-64
- ./install_mvn
- For linux-x86-64 and osx-x86-64
- chmod +x *.sh (to make sure the scripts are executable)
- ./install_mvn.sh
- For win-x86-64
Deploying X jars into your Remote Maven Repository
- Download the X distribution using one of the following links depending on the platform for which jars need to be installed into your Maven repository
- Un-archive the distribution and execute the following command from the root of the extracted bundle:
- For win-x86-64
- ./install_mvn -mode deploy -repoId <repository Id> -repoUrl <repository URL>
- For linux-x86-64 and osx-x86-64
- chmod +x *.sh (to make sure the scripts are executable)
- ./install_mvn.sh -mode deploy -repoId <repository Id> -repoUrl <repository URL>
- For win-x86-64
Dependencies
Talon
Talon contains the platform's runtime kernel and is need for all X applications:
Linux Native Libraries
The following dependency can be used to improve performance and is required in some cases for zero garbage operation. This can be place on the classpath with nvx-talon-all
Solace Binding
Optionally, if you are using solace as your messaging backbone, you should add the nvx-solace dependency:
JMS Binding
Optionally, if you are using jms as your messaging backbone, you should add the nvx-jms dependency.
Core X (Deprecated)
The nvx-core-all jar includes nvx-talon, but additionally bundles the solace message bus binding. 3.X releases have begun the process of phasing out nvx-core, so nvx-talon-all should be used instead.