Phonetic-Plugin in Maven-Repository is outdated

https://www.elastic.co/guide/en/elasticsearch/plugins/current/analysis-phonetic.html
http://mvnrepository.com/artifact/org.elasticsearch.plugin/analysis-phonetic

I can download the current version from your Website, but maven central (which we use to setup our integration tests) lists 5.0.0-alpha5 as the newest version.

Is there a specific reason for this?

It's not recommended to run elasticsearch embedded.

The official download link is https://artifacts.elastic.co/downloads/elasticsearch-plugins/analysis-phonetic/analysis-phonetic-5.1.1.zip

But may be you can try:

   <repositories>
      <!-- add the elasticsearch repo -->
      <repository>
         <id>elasticsearch-releases</id>
         <url>https://artifacts.elastic.co/maven</url>
         <releases>
            <enabled>true</enabled>
         </releases>
         <snapshots>
            <enabled>false</enabled>
         </snapshots>
      </repository>
      ...
   </repositories>

HTH

Thank you for your information.
This applies for integration testing regardless of running embedded or not. We are currently unpacking the plugins to the plugins dir via unpack-dependencies.
Like http://david.pilato.fr/blog/2016/10/18/elasticsearch-real-integration-tests-updated-for-ga/

However, I cannot find the analysis-phonetic plugin on this maven server either. Browsing is disabled.
404:
https://artifacts.elastic.co/maven/org/elasticsearch/plugin/analysis-phonetic/5.0.0/analysis-phonetic-5.0.0.pom
https://artifacts.elastic.co/maven/org/elasticsearch/plugin/analysis-phonetic/5.1.1/analysis-phonetic-5.1.1.pom
Also tried .zip/jar
Works:
https://artifacts.elastic.co/maven/org/elasticsearch/plugin/transport-netty3-client/5.0.0/transport-netty3-client-5.0.0.pom

        <dependency>
          <groupId>org.elasticsearch.plugin</groupId>
          <artifactId>analysis-phonetic</artifactId>
          <version>5.1.1</version>
          <-- Tried with and without zip -->
          <type>zip</type>
        </dependency>
1 Like

@dadoonet
We have now "solved" this by creating our own artifact and deploying it to our Nexus.
The "offline install" package was used as the base.

1 Like

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.