Transitive Dependency: Using Elasticsearch Rest High Client problem in AEM

前端 未结 1 682
谎友^
谎友^ 2021-02-06 13:52

I am trying to use Java High Level Rest Client in Adobe Experience Manager to finish project of comparison between Lucene, Solr and Elasticsearch search

相关标签:
1条回答
  • 2021-02-06 14:21

    So my guess was right, transitive dependencies were not included altho <Embed-Transitive>true</Embed-Transitive> exists.

    The following is necessary when running elasticsearch as a search engine on AEM the problem:

    • I have added all transitive dependencies in pom.xml (versions are defined in parent/pom.xml):

        <!-- Elasticsearch -->
            <dependency>
                <groupId>org.elasticsearch.client</groupId>
                <artifactId>elasticsearch-rest-high-level-client</artifactId>
            </dependency>
            <dependency>
                <groupId>org.elasticsearch.client</groupId>
                <artifactId>elasticsearch-rest-client</artifactId>
            </dependency>
            <dependency>
                <groupId>org.elasticsearch</groupId>
                <artifactId>elasticsearch</artifactId>
            </dependency>
            <dependency>
                <groupId>org.elasticsearch</groupId>
                <artifactId>elasticsearch-x-content</artifactId>
            </dependency>
            <dependency>
                <groupId>org.elasticsearch.plugin</groupId>
                <artifactId>rank-eval-client</artifactId>
            </dependency>
            <dependency>
                <groupId>org.apache.commons</groupId>
                <artifactId>commons-imaging</artifactId>
                <scope>test</scope>
            </dependency>
            <dependency>
                <groupId>org.elasticsearch.plugin</groupId>
                <artifactId>lang-mustache-client</artifactId>
            </dependency>
            <dependency>
                <groupId>org.apache.httpcomponents</groupId>
                <artifactId>httpasyncclient</artifactId>
            </dependency>
      

    It is important to add all third-party dependencies as <Embed-Dependency> inside maven-bundle-plugin like this:

        <plugin>
            <groupId>org.apache.felix</groupId>
            <artifactId>maven-bundle-plugin</artifactId>
            <extensions>true</extensions>
            <configuration>
                <instructions>
                    <Embed-Dependency>org.apache.servicemix.bundles.solr-solrj, noggit,
                        elasticsearch-rest-high-level-client,
                        elasticsearch,
                        elasticsearch-rest-client,
                        elasticsearch-x-content,
                        elasticsearch-core,
                        rank-eval-client,
                        lang-mustache-client,
                        httpasyncclient;
                    </Embed-Dependency>
                    <Embed-Transitive>true</Embed-Transitive>
                    <Embed-Directory>OSGI-INF/lib</Embed-Directory>
                    <Export-Package>we.retail.core.model*</Export-Package>
                    <Import-Package>
                        *;resolution:=optional
                    </Import-Package>
                    <Private-Package>
                        we.retail.core*
                    </Private-Package>
                    <Sling-Model-Packages>
                        we.retail.core.model
                    </Sling-Model-Packages>
                    <_fixupmessages>"Classes found in the wrong directory";is:=warning</_fixupmessages>
                </instructions>
            </configuration>
        </plugin>
    

    Important to notice:

    • All third-party dependencies (the ones outside of OSGi) must be included in the "Embed-Dependency"
    • "Embed-Transitive" must be set to true to include transitive dependencies
    • "Import-Package" must include "*;resolution:=optional" to exclude all dependencies that could not be resolved so that the program can run normally
    • For some reason, there was an error in compile time when "elasticsearch" dependency was added which is not important for this task, so I've decided to ignore it this way:
    <_fixupmessages>"Classes found in the wrong directory";is:=warning</_fixupmessages>
    

    Though challenging, I finally resolved it. There are many similar or the same problems on Google, so I hope this will help someone. Thanks to everyone that tried to help.

    0 讨论(0)
提交回复
热议问题