OpenSearch/plugins/analysis-phonetic/pom.xml

39 lines
1.3 KiB
XML
Raw Normal View History

2012-01-07 16:06:50 -05:00
<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
<parent>
[maven] change groupId / artifactId When we generate our project, we can get something like: ``` ├── dev-tools ├── elasticsearch ├── elasticsearch-parent ├── elasticsearch-plugin ├── plugin │   ├── elasticsearch-analysis-icu │   ├── elasticsearch-analysis-kuromoji │   ├── elasticsearch-analysis-phonetic │   ├── elasticsearch-analysis-smartcn │   ├── elasticsearch-analysis-stempel │   ├── elasticsearch-cloud-aws │   ├── elasticsearch-cloud-azure │   ├── elasticsearch-cloud-gce │   ├── elasticsearch-delete-by-query │   ├── elasticsearch-lang-javascript │   └── elasticsearch-lang-python ├── rest-api-spec └── securemock ``` I propose here to use a common naming for artifacts: start always with `elasticsearch-`. Also, move `elasticsearch-plugin` to `org.elasticsearch.plugin` groupId. So we could have: ``` ├── elasticsearch ├── elasticsearch-dev-tools ├── elasticsearch-parent ├── elasticsearch-rest-api-spec ├── elasticsearch-securemock ├── plugin │   ├── elasticsearch-analysis-icu │   ├── elasticsearch-analysis-kuromoji │   ├── elasticsearch-analysis-phonetic │   ├── elasticsearch-analysis-smartcn │   ├── elasticsearch-analysis-stempel │   ├── elasticsearch-cloud-aws │   ├── elasticsearch-cloud-azure │   ├── elasticsearch-cloud-gce │   ├── elasticsearch-delete-by-query │   ├── elasticsearch-lang-javascript │   ├── elasticsearch-lang-python │   └── elasticsearch-plugin ```
2015-07-03 14:00:32 -04:00
<groupId>org.elasticsearch.plugin</groupId>
2015-05-21 22:51:16 -04:00
<artifactId>elasticsearch-plugin</artifactId>
<version>2.0.0-SNAPSHOT</version>
</parent>
[maven] change groupId / artifactId When we generate our project, we can get something like: ``` ├── dev-tools ├── elasticsearch ├── elasticsearch-parent ├── elasticsearch-plugin ├── plugin │   ├── elasticsearch-analysis-icu │   ├── elasticsearch-analysis-kuromoji │   ├── elasticsearch-analysis-phonetic │   ├── elasticsearch-analysis-smartcn │   ├── elasticsearch-analysis-stempel │   ├── elasticsearch-cloud-aws │   ├── elasticsearch-cloud-azure │   ├── elasticsearch-cloud-gce │   ├── elasticsearch-delete-by-query │   ├── elasticsearch-lang-javascript │   └── elasticsearch-lang-python ├── rest-api-spec └── securemock ``` I propose here to use a common naming for artifacts: start always with `elasticsearch-`. Also, move `elasticsearch-plugin` to `org.elasticsearch.plugin` groupId. So we could have: ``` ├── elasticsearch ├── elasticsearch-dev-tools ├── elasticsearch-parent ├── elasticsearch-rest-api-spec ├── elasticsearch-securemock ├── plugin │   ├── elasticsearch-analysis-icu │   ├── elasticsearch-analysis-kuromoji │   ├── elasticsearch-analysis-phonetic │   ├── elasticsearch-analysis-smartcn │   ├── elasticsearch-analysis-stempel │   ├── elasticsearch-cloud-aws │   ├── elasticsearch-cloud-azure │   ├── elasticsearch-cloud-gce │   ├── elasticsearch-delete-by-query │   ├── elasticsearch-lang-javascript │   ├── elasticsearch-lang-python │   └── elasticsearch-plugin ```
2015-07-03 14:00:32 -04:00
<artifactId>elasticsearch-analysis-phonetic</artifactId>
<name>Elasticsearch Phonetic Analysis plugin</name>
<description>The Phonetic Analysis plugin integrates phonetic token filter analysis with elasticsearch.</description>
2012-01-07 16:06:50 -05:00
<properties>
<tests.rest.suite>analysis_phonetic</tests.rest.suite>
<tests.rest.load_packaged>false</tests.rest.load_packaged>
</properties>
2012-01-07 16:06:50 -05:00
<dependencies>
<dependency>
<groupId>org.apache.lucene</groupId>
<artifactId>lucene-analyzers-phonetic</artifactId>
2012-01-07 16:06:50 -05:00
</dependency>
</dependencies>
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
2012-01-07 16:06:50 -05:00
<artifactId>maven-assembly-plugin</artifactId>
</plugin>
</plugins>
</build>
2015-01-02 14:40:18 -05:00
</project>