OpenSearch/plugins/cloud-aws/pom.xml

55 lines
2.0 KiB
XML
Raw Normal View History

2011-12-05 08:42:33 -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>
2015-03-25 04:56:34 -04:00
<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:52 -04:00
<artifactId>elasticsearch-plugin</artifactId>
<version>2.0.0.beta1-SNAPSHOT</version>
2015-03-25 04:56:34 -04:00
</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-cloud-aws</artifactId>
<name>Elasticsearch AWS cloud plugin</name>
<description>The Amazon Web Service (AWS) Cloud plugin allows to use AWS API for the unicast discovery mechanism and add S3 repositories.</description>
2011-12-05 08:42:33 -05:00
<properties>
<amazonaws.version>1.10.0</amazonaws.version>
<tests.jvms>1</tests.jvms>
2015-07-07 13:03:37 -04:00
<tests.rest.suite>cloud_aws</tests.rest.suite>
<tests.rest.load_packaged>false</tests.rest.load_packaged>
2011-12-05 08:42:33 -05:00
</properties>
<dependencies>
<!-- AWS SDK -->
2011-12-05 08:42:33 -05:00
<dependency>
<groupId>com.amazonaws</groupId>
<artifactId>aws-java-sdk-ec2</artifactId>
<version>${amazonaws.version}</version>
</dependency>
<dependency>
<groupId>com.amazonaws</groupId>
<artifactId>aws-java-sdk-s3</artifactId>
<version>${amazonaws.version}</version>
2011-12-05 08:42:33 -05:00
</dependency>
<!-- We need to force here the compile scope as it was defined as test scope in plugins/pom.xml -->
<!-- TODO: remove this dependency when we will have a REST Test module -->
<dependency>
<groupId>org.apache.httpcomponents</groupId>
<artifactId>httpclient</artifactId>
<scope>compile</scope>
</dependency>
2011-12-05 08:42:33 -05:00
</dependencies>
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
2011-12-05 08:42:33 -05:00
<artifactId>maven-assembly-plugin</artifactId>
</plugin>
</plugins>
</build>
2015-01-02 15:10:01 -05:00
</project>