Hot fixes are released jar files to address a bug in a specific version, without needing to advance versions.
On this page:
The available hot fixes are shown in the tables below.
|Bundle||Version||Base version||Description of update|
|aspire-app-group-expansion-manager||18.104.22.168||2.0.3||Made compatible with aspire-ldap version 22.214.171.124. Updated to allow passing of number of retries and retry delay parameters|
NOTE: this fix requires version 126.96.36.199 of aspire-ldap, aspire-ldap-cache and aspire-apacheds
|aspire-app-group-expansion-manager||188.8.131.52||2.0.3||Added an option to disable the connection to LDAP|
|aspire-apacheds||184.108.40.206||2.0.3||Made compatible with aspire-ldap version 220.127.116.11|
NOTE: this fix requires version 18.104.22.168 of aspire-ldap
|aspire-application||22.214.171.124||2.0.1||Fixed issues with scheduled jobs getting fired in the middle of a crawl, and content sources getting deleted when an invalid xml file was found|
|aspire-application||126.96.36.199||2.0.1||Fixed issue related to null pointer exceptions when loading corrupted content sources.|
|aspire-confluence-connector||188.8.131.52||1.3||Custom version with several fixes for the Aspire-Attivio connector wrapper.|
|aspire-eroom-connector||184.108.40.206||2.0.1||Custom SpecialAcls, fix @domain issue for GE and fix some timeouts|
|app-eroom-connector||220.127.116.11||2.0.3||Added EroomETMaxSize field in dxf to set the max extract text size.|
|aspire-eroom-connector||18.104.22.168||2.0.3||Fixed issue with static mapDB for ACLs|
|aspire-eroom-connector||22.214.171.124||126.96.36.199||Added option to skip the links items from the crawl results|
|aspire-groovy||188.8.131.52||2.0.2||Fixed an issue where returning JSON transformers to a pool caused random exceptions|
NOTE: this fix is required when using aspire-post-http version 184.108.40.206
|aspire-heritrix-connector||220.127.116.11||2.0.1||Added feature to the Heritrix Engine to prefer non DNS resolves, (prefer the hosts file)|
|aspire-jive-connector||18.104.22.168||2.0.3||Fixed issue with UserOrGroup throwing ClassNotFoundException|
|aspire-jive-connector||22.214.171.124||2.0||Added support for custom types|
|aspire-jive-connector||126.96.36.199||2.0||Added the ability to select which endpoints the user wants to crawl|
|aspire-ldap||188.8.131.52||2.0.3||Updated to fix and issue with re-connections to ldap. The retry parameters are now configurable|
|aspire-ldap-cache||184.108.40.206||2.0.3||Made compatible with aspire-ldap version 220.127.116.11|
NOTE: this fix requires version 18.104.22.168 of aspire-ldap
|aspire-post-http||22.214.171.124||2.0.2||Ported changes allowing uses with ElasticSearch from 2.1|
NOTE: this fix has a bug that causes random exceptions. Use version 126.96.36.199 instead
|aspire-post-http||188.8.131.52||2.0.2||Ported changes allowing uses with ElasticSearch from 2.1|
NOTE: this fix requires version 184.108.40.206 of aspire-groovy
|aspire-rdb-connector||220.127.116.11||2.0||Fixed an issue where the rdb scanner was never finishing|
|aspire-scanner||18.104.22.168||2.0.3||Fixed issue with UserOrGroup throwing ClassNotFoundException|
|aspire-scanner||22.214.171.124||2.0.1||SpecialAcls change byte to String|
|aspire-scanner||126.96.36.199||2.0.1||Small fix to add name property to SourceItem for hierarchy calculations and sets the snapshot separator as public.|
|aspire-sharepoint-connector||188.8.131.52||2.0.1||Migrates the SharePoint Scanner from Hierarchical Scanner to Push Scanner to be able to use SharePoint change tokens for snapshot files. Adds the possibility to crawl from 1 or more site collections using the same content source. It also has the option to "discover" all site collections inside a Web Application.|
|aspire-sharepoint-connector||184.108.40.206||2.0||Fixes an issue where the SharePoint connector crashes while crawling after a SOAP exception|
|aspire-sharepoint-connector||220.127.116.11||1.3||Custom version with several fixes for the Aspire-Attivio connector wrapper.|
|aspire-simple-group-expander||18.104.22.168||2.0.1||SpecialAcls change byte to String|
|aspire-simple-group-expander||22.214.171.124||2.0.3||Fixed issue with UserOrGroup throwing ClassNotFoundException|
Note: Typically, these fixes are not cumulative. A hot fix at version 126.96.36.199 will not include the fixes made in 188.8.131.52, 184.108.40.206 etc. You should check the base version to be certain.
Hot fixes can be installed using the <bundleVersions> tag in the settings.xml file in the config directory. See here for full details.
You will need to add a section to the <repository> identifying the bundle, and version you wish to use.
Example: To use a hot fix for the eRoom connector, add the following to the settings.xml file:
<bundleVersions> <bundle artifactId="aspire-eroom-connector" version="220.127.116.11"/> </bundleVersions>
Note: replace 18.104.22.168 with the version of the fix you require.
<repository type="maven"> <defaultVersion>2.0.1</defaultVersion> <bundleVersions> <bundle artifactId="aspire-eroom-connector" version="22.214.171.124"/> </bundleVersions> <remoteRepository> <id>stPublic</id> <url>http://repository.searchtechnologies.com/artifactory/simple/community-public/</url> <user>YOUR-REGISTERED-USERNAME</user> <password>YOUR-REGISTERED-PASSWORD</password> </remoteRepository> <repository>
If you are using Aspire in offline mode, you only need to add the hot fixes jars to the bundles/Aspire folder of the distribution.
You should have the following for both online and offline mode:
<repositories> <bundleVersions> <bundle artifactId="aspire-eroom-connector" version="126.96.36.199"/> </bundleVersions> <repository type="distribution"> ... </repository> <repository type="maven"> ... </repository> <repositories>