Jive EAE/Search Dependency Map

Version 12

    It's important to get your version mapping right when building and running your local Jive instance.  Each version of the Jive platform needs a particular version of the Enterprise Activity Engine (EAE) and local search server (for 6.0 and up).

     

    Managing these versions is pretty simple.  It just depends on what version of the Jive Maven Archetype you used to create your project.

     

    6.0.x/7.0.x

    Both the EAE and Search servers are defined in pom.xml file in your project's run-services module.  Each service is defined as a separate profile, local for Search, and eae for EAE.  Within each profile, there is a single dependency for the library required to run the server locally.  This is where the version for each server is defined.

     

    Search Server

    <profile>
        <id>local</id>
            <dependencies>
        <dependency>
                <groupId>com.jivesoftware.service.deployable.on-prem-all-in-one-search</groupId>
                    <artifactId>on-prem-all-in-one-search-main</artifactId>
                    <version>${search.version}</version>
                    <scope>test</scope>
                </dependency>
            </dependencies>
    ...
    
    
    
    
    
    
    
    
    
    
    
    
    

     

    EAE Server

    <profile>
        <id>eae</id>
        <dependencies>
            <dependency>
                <groupId>eae.core</groupId>
                <artifactId>eae-service</artifactId>
                <version>${eae.version}</version>
                <classifier>shaded</classifier>
            </dependency>
        </dependencies>
    
    
    
    
    
    
    
    
    
    
    
    
    

     

    You can see here that in both cases the values of the <version> elements are variables, ${search.version} and ${eae.version}.  These are defined in your project's root pom.xml file.

        <properties>
            ...
            <jive.version>6.0.1.1</jive.version>
            <eae.version>3.2.1.18</eae.version>
            <search.version>2.15.32.7-synonyms.6</search.version>
    ...
    </properties>
    
    
    
    
    
    
    
    
    
    
    
    
    

     

    5.0.x

    In 5.0.x, the EAE service definition lives in the web module's pom.xml file, but gets its version from the project's root pom.xml, which is defined as a dependency.

    <dependencyManagement>
        <dependencies>
    ...
    <dependency>
                <groupId>eae.core</groupId>
                <artifactId>eae-service</artifactId>
                <version>1.3.4.2</version> 
            </dependency>
    ...
    </dependencies>
    </dependencyManagement>
    
    
    
    
    
    
    
    
    
    
    
    

     

    Here is a table that lists the valid combinations of version numbers:

     

    Jive Versioneae-service versionon-prem-all-in-one-search-main version
    7.0.2.07.0.0.07.0.1.0.9
    7.0.1.17.0.0.07.0.1.0.9
    7.0.1.07.0.0.07.0.1.0.9
    7.0.0.34.4.0.57.0.0.0.1
    7.0.0.24.4.0.57.0.0.0.1
    7.0.0.14.4.0.57.0.0.0.1
    7.0.0.04.4.0.52.15.32.7-synonyms.7
    6.0.4.23.2.4.72.15.32.7-synonyms.10
    6.0.4.13.2.4.72.15.32.7-synonyms.9
    6.0.4.03.2.3.92.15.32.7-synonyms.9
    6.0.3.43.2.3.92.15.32.7-synonyms.8
    6.0.3.33.2.3.92.15.32.7-synonyms.8
    6.0.3.23.2.3.92.15.32.7-synonyms.8
    6.0.3.13.2.3.92.15.32.7-synonyms.6 or 2.15.32.7-synonyms.7
    6.0.3.03.2.3.82.15.32.7-synonyms.6 or 2.15.32.7-synonyms.7
    6.0.2.03.2.2.22.15.32.7-synonyms.6 or 2.15.32.7-synonyms.7
    6.0.1.23.2.1.182.15.32.7-synonyms.6 or 2.15.32.7-synonyms.7
    6.0.1.13.2.1.182.15.32.7-synonyms.6 or 2.15.32.7-synonyms.7
    6.0.1.03.2.1.182.15.32.7-synonyms.6 or 2.15.32.7-synonyms.7
    6.0.0.13.2.0.20
    6.0.0.03.2.0.182.10.30.2
    5.0.61.3.5.5n/a
    5.0.51.3.4.2n/a
    5.0.41.3.3.4n/a
    5.0.31.3.2.0n/a
    5.0.21.3.0.1n/a
    5.0.1.11.2.0.3n/a
    5.0.11.2.0.2n/a