Page tree
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

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

Page currently under constructionUNDER CONSTRUCTION


On this page:

Available Hot Fixes


The available hot fixes are shown in the tables below.

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

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

aspire-app-group-expansion-manager2.0.3.12.0.3Added an option to disable the connection to LDAP
aspire-apacheds2.0.3.72.0.3Made compatible with aspire-ldap version 2.0.3.7

NOTE: this fix requires version 2.0.3.7 of aspire-ldap

aspire-application2.0.1.12.0.1Fixed 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-application2.0.1.22.0.1Fixed issue related to null pointer exceptions when loading corrupted content sources.
aspire-confluence-connector1.3.0.21.3Custom version with several fixes for the Aspire-Attivio connector wrapper.
aspire-eroom-connector2.0.1.22.0.1Custom SpecialAcls, fix @domain issue for GE and fix some timeouts
app-eroom-connector2.0.3.12.0.3Added EroomETMaxSize field in dxf to set the max extract text size.
aspire-eroom-connector2.0.3.12.0.3Fixed issue with static mapDB for ACLs
aspire-eroom-connector2.0.3.52.0.3.4Added option to skip the links items from the crawl results
aspire-groovy2.0.2.12.0.2Fixed an issue where returning JSON transformers to a pool caused random exceptions

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

aspire-heritrix-connector2.0.1.12.0.1Added feature to the Heritrix Engine to prefer non DNS resolves, (prefer the hosts file)
aspire-jive-connector2.0.3.12.0.3Fixed issue with UserOrGroup throwing ClassNotFoundException
aspire-jive-connector2.0.0.22.0Added support for custom types
aspire-jive-connector2.0.0.12.0Added the ability to select which endpoints the user wants to crawl
aspire-ldap2.0.3.72.0.3Updated to fix and issue with re-connections to ldap. The retry parameters are now configurable
aspire-ldap-cache2.0.3.72.0.3Made compatible with aspire-ldap version 2.0.3.7

NOTE: this fix requires version 2.0.3.7 of aspire-ldap

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

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

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

NOTE: this fix requires version 2.0.2.1 of aspire-groovy

aspire-rdb-connector2.0.0.12.0Fixed an issue where the rdb scanner was never finishing
aspire-scanner2.0.3.12.0.3Fixed issue with UserOrGroup throwing ClassNotFoundException
aspire-scanner2.0.1.22.0.1SpecialAcls change byte[] to String
aspire-scanner2.0.1.12.0.1Small fix to add name property to SourceItem for hierarchy calculations and sets the snapshot separator as public.
aspire-sharepoint-connector2.0.1.12.0.1Migrates 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.0.0.12.0Fixes an issue where the SharePoint connector crashes while crawling after a SOAP exception
aspire-sharepoint-connector1.3.0.21.3Custom version with several fixes for the Aspire-Attivio connector wrapper.
aspire-simple-group-expander2.0.1.22.0.1SpecialAcls change byte[] to String
aspire-simple-group-expander2.0.3.12.0.3Fixed issue with UserOrGroup throwing ClassNotFoundException

 

Note: Typically, these fixes are not cumulative. A hot fix at version 2.0.1.5 will not include the fixes made in 2.0.1.1, 2.0.1.2 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:

<bundleVersions>
  <bundle artifactId="aspire-eroom-connector" version="2.0.1.1"/>
</bundleVersions>

Note: replace 2.0.1.1 with the version of the fix you require.

Settings file with hot fix installed

<repository type="maven">
  <defaultVersion>2.0.1</defaultVersion>
  <bundleVersions>
    <bundle artifactId="aspire-eroom-connector" version="2.0.1.1"/>
  </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="2.0.1.1"/>
  </bundleVersions>
  <repository type="distribution">
    ...
  </repository>
  <repository type="maven">
    ...
  </repository>
<repositories>

Using Hot Fixes for Aspire-application




  • No labels