OpenSearch/plugins/cloud-gce/pom.xml

70 lines
2.9 KiB
XML
Raw Normal View History

<?xml version="1.0" encoding="UTF-8"?>
<!-- Licensed to Elasticsearch under one or more contributor
license agreements. See the NOTICE file distributed with this work for additional
information regarding copyright ownership. Elasticsearch licenses this file to you
under the Apache License, Version 2.0 (the "License"); you may not use this
file except in compliance with the License. You may obtain a copy of the
License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by
applicable law or agreed to in writing, software distributed under the License
is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied. See the License for the specific language
governing permissions and limitations under the License. -->
<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 10:40:58 -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:52:31 -04:00
<artifactId>elasticsearch-plugin</artifactId>
<version>2.0.0-beta1-SNAPSHOT</version>
2015-03-25 10:40:58 -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-gce</artifactId>
<name>Elasticsearch Google Compute Engine cloud plugin</name>
<description>The Google Compute Engine (GCE) Cloud plugin allows to use GCE API for the unicast discovery mechanism.</description>
<properties>
<google.gce.version>v1-rev59-1.20.0</google.gce.version>
<es.plugin.port>9300</es.plugin.port>
<!-- currently has no unit tests -->
<tests.ifNoTests>warn</tests.ifNoTests>
<tests.jvms>1</tests.jvms>
2015-07-07 13:03:37 -04:00
<tests.rest.suite>cloud_gce</tests.rest.suite>
<tests.rest.load_packaged>false</tests.rest.load_packaged>
</properties>
<dependencies>
<!-- Google APIs -->
<dependency>
<groupId>com.google.apis</groupId>
<artifactId>google-api-services-compute</artifactId>
<version>${google.gce.version}</version>
<exclusions>
<exclusion>
<groupId>com.google.guava</groupId>
<artifactId>guava-jdk5</artifactId>
</exclusion>
</exclusions>
</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>
</dependencies>
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-assembly-plugin</artifactId>
</plugin>
</plugins>
</build>
</project>