Page tree

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.

Hot fixes are released jar files to address a bug in a specific version, without needing to advance versions. 

Page currently under constructionImage Added

titleUnder Construction

On this page:

Table of Contents

Page currently under constructionImage Removed

This page is currently under construction

Available Hot Fixes

The available hot fixes are shown in the tables below.

BundleVersionBase versionDescription of update
app-group-expansion-manager2. compatible with aspire-ldap version Updated to allow passing of number of retries and retry delay parameters

NOTE: this fix requires version of aspire-ldap, aspire-ldap-cache and aspire-apacheds

aspire-app-group-expansion-manager2. an option to disable the connection to LDAPaspire-apacheds2. compatible with aspire-ldap version

NOTE: this fix requires version of aspire-ldap

aspire-application2. issues with scheduled jobs getting fired in the middle of a crawl, and content sources getting deleted when an invalid xml file was foundaspire-application2. issue related to null pointer exceptions when loading corrupted content sources.aspire-confluence-connector1. version with several fixes for the Aspire-Attivio connector wrapper.aspire-eroom-connector2. SpecialAcls, fix @domain issue for GE and fix some timeoutsapp-eroom-connector2. EroomETMaxSize field in dxf to set the max extract text size.aspire-eroom-connector2. issue with static mapDB for ACLsaspire-eroom-connector2. option to skip the links items from the crawl resultsaspire-groovy2. an issue where returning JSON transformers to a pool caused random exceptions

NOTE: this fix is required when using aspire-post-http version

aspire-heritrix-connector2. feature to the Heritrix Engine to prefer non DNS resolves, (prefer the hosts file)aspire-jive-connector2. issue with UserOrGroup throwing ClassNotFoundExceptionaspire-jive-connector2. support for custom typesaspire-jive-connector2. the ability to select which endpoints the user wants to crawlaspire-ldap2. to fix and issue with re-connections to ldap. The retry parameters are now configurableaspire-ldap-cache2. compatible with aspire-ldap version

NOTE: this fix requires version of aspire-ldap

aspire-post-http2. changes allowing uses with ElasticSearch from 2.1

NOTE: this fix has a bug that causes random exceptions. Use version instead

aspire-post-http2. changes allowing uses with ElasticSearch from 2.1

NOTE: this fix requires version of aspire-groovy

aspire-rdb-connector2. an issue where the rdb scanner was never finishingaspire-scanner2. issue with UserOrGroup throwing ClassNotFoundExceptionaspire-scanner2. change byte[] to Stringaspire-scanner2. fix to add name property to SourceItem for hierarchy calculations and sets the snapshot separator as public.aspire-sharepoint-connector2. 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-connector2. an issue where the SharePoint connector crashes while crawling after a SOAP exceptionaspire-sharepoint-connector1. version with several fixes for the Aspire-Attivio connector wrapper.aspire-simple-group-expander2. change byte[] to Stringaspire-simple-group-expander2. issue with UserOrGroup throwing ClassNotFoundException


jive-source3. option to crawl multiple Jive Places.

Note: Typically, these fixes are not cumulative. A hot fix at version will not include the fixes made in, etc. You should check the base version to be certain.

Using Hot Fixes

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:

  <bundle artifactId="aspire-eroom-connector" version="2x.0.1.1"/>

Note: replace 2x.0.1.1 with the version of the fix you require.

Settings file with hot fix installed

<repository type="maven">
    <bundle artifactId="aspire-eroom-connector" version="2x.0.1.1"/>


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:

    <bundle artifactId="aspire-eroom-connector" version="2x.0.1.1"/>
  <repository type="distribution">
  <repository type="maven">

Using Hot Fixes for