honeymoose
/
OpenSearch
mirror of https://github.com/honeymoose/OpenSearch.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
OpenSearch/pom.xml

274 lines
12 KiB
XML
Raw Normal View History

Add cloud discovery for google compute engine Google Compute Engine VM discovery allows to use the google APIs to perform automatic discovery (similar to multicast in non hostile multicast environments). Here is a simple sample configuration: ```yaml cloud: gce: project_id: <your-google-project-id> zone: <your-zone> discovery: type: gce ``` How to start (short story) -------------------------- * Create Google Compute Engine instance * Install Elasticsearch * Install Google Compute Engine Cloud plugin * Modify `elasticsearch.yml` file * Start Elasticsearch Closes #1.
2013-06-28 03:45:02 -04:00
<?xml version="1.0" encoding="UTF-8"?>
Move tests to elasticsearch test framework Closes #8.
2014-01-13 10:07:27 -05:00
<!-- Licensed to Elasticsearch under one or more contributor
Add cloud discovery for google compute engine Google Compute Engine VM discovery allows to use the google APIs to perform automatic discovery (similar to multicast in non hostile multicast environments). Here is a simple sample configuration: ```yaml cloud: gce: project_id: <your-google-project-id> zone: <your-zone> discovery: type: gce ``` How to start (short story) -------------------------- * Create Google Compute Engine instance * Install Elasticsearch * Install Google Compute Engine Cloud plugin * Modify `elasticsearch.yml` file * Start Elasticsearch Closes #1.
2013-06-28 03:45:02 -04:00
license agreements. See the NOTICE file distributed with this work for additional
Move tests to elasticsearch test framework Closes #8.
2014-01-13 10:07:27 -05:00
information regarding copyright ownership. Elasticsearch licenses this file to you
Add cloud discovery for google compute engine Google Compute Engine VM discovery allows to use the google APIs to perform automatic discovery (similar to multicast in non hostile multicast environments). Here is a simple sample configuration: ```yaml cloud: gce: project_id: <your-google-project-id> zone: <your-zone> discovery: type: gce ``` How to start (short story) -------------------------- * Create Google Compute Engine instance * Install Elasticsearch * Install Google Compute Engine Cloud plugin * Modify `elasticsearch.yml` file * Start Elasticsearch Closes #1.
2013-06-28 03:45:02 -04:00
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>
Depend on elasticsearch-parent To simplify plugins maintenance and provide more value in the future, we are starting to build an `elasticsearch-parent` project. This commit is the first step for this plugin to depend on this new `pom` maven project.
2015-01-02 15:30:46 -05:00
<parent>
<groupId>org.elasticsearch</groupId>
<artifactId>elasticsearch-parent</artifactId>
<version>2.0.0-SNAPSHOT</version>
</parent>
Add cloud discovery for google compute engine Google Compute Engine VM discovery allows to use the google APIs to perform automatic discovery (similar to multicast in non hostile multicast environments). Here is a simple sample configuration: ```yaml cloud: gce: project_id: <your-google-project-id> zone: <your-zone> discovery: type: gce ``` How to start (short story) -------------------------- * Create Google Compute Engine instance * Install Elasticsearch * Install Google Compute Engine Cloud plugin * Modify `elasticsearch.yml` file * Start Elasticsearch Closes #1.
2013-06-28 03:45:02 -04:00
<groupId>org.elasticsearch</groupId>
<artifactId>elasticsearch-cloud-gce</artifactId>
Update to elasticsearch master
2014-03-26 15:16:11 -04:00
<version>3.0.0-SNAPSHOT</version>
Add cloud discovery for google compute engine Google Compute Engine VM discovery allows to use the google APIs to perform automatic discovery (similar to multicast in non hostile multicast environments). Here is a simple sample configuration: ```yaml cloud: gce: project_id: <your-google-project-id> zone: <your-zone> discovery: type: gce ``` How to start (short story) -------------------------- * Create Google Compute Engine instance * Install Elasticsearch * Install Google Compute Engine Cloud plugin * Modify `elasticsearch.yml` file * Start Elasticsearch Closes #1.
2013-06-28 03:45:02 -04:00
Add plugin release semi-automatic script Closes #13.
2014-03-11 12:39:10 -04:00
<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>
<url>https://github.com/elasticsearch/elasticsearch-cloud-gce/</url>
Add cloud discovery for google compute engine Google Compute Engine VM discovery allows to use the google APIs to perform automatic discovery (similar to multicast in non hostile multicast environments). Here is a simple sample configuration: ```yaml cloud: gce: project_id: <your-google-project-id> zone: <your-zone> discovery: type: gce ``` How to start (short story) -------------------------- * Create Google Compute Engine instance * Install Elasticsearch * Install Google Compute Engine Cloud plugin * Modify `elasticsearch.yml` file * Start Elasticsearch Closes #1.
2013-06-28 03:45:02 -04:00
<inceptionYear>2013</inceptionYear>
<licenses>
<license>
<name>The Apache Software License, Version 2.0</name>
<url>http://www.apache.org/licenses/LICENSE-2.0.txt</url>
<distribution>repo</distribution>
</license>
</licenses>
<scm>
<connection>scm:git:git@github.com:elasticsearch/elasticsearch-cloud-gce.git</connection>
<developerConnection>scm:git:git@github.com:elasticsearch/elasticsearch-cloud-gce.git</developerConnection>
<url>http://github.com/elasticsearch/elasticsearch-cloud-gce</url>
</scm>
<issueManagement>
<system>GitHub</system>
<url>https://github.com/elasticsearch/elasticsearch-cloud-gce/issues/</url>
</issueManagement>
<properties>
Upgrade to GCE v1-rev15-1.18.0-rc API Closes #19.
2014-04-14 17:36:24 -04:00
<google.gce.version>v1-rev15-1.18.0-rc</google.gce.version>
<google.api.version>1.18.0-rc</google.api.version>
Move tests to elasticsearch test framework Closes #16.
2014-03-12 07:03:27 -04:00
<es.plugin.port>9300</es.plugin.port>
Add cloud discovery for google compute engine Google Compute Engine VM discovery allows to use the google APIs to perform automatic discovery (similar to multicast in non hostile multicast environments). Here is a simple sample configuration: ```yaml cloud: gce: project_id: <your-google-project-id> zone: <your-zone> discovery: type: gce ``` How to start (short story) -------------------------- * Create Google Compute Engine instance * Install Elasticsearch * Install Google Compute Engine Cloud plugin * Modify `elasticsearch.yml` file * Start Elasticsearch Closes #1.
2013-06-28 03:45:02 -04:00
</properties>
<dependencies>
Fix tests When upgrading to elasticsearch 1.2.1 test framework, some tests are not working anymore because of `ElasticsearchIntegrationTest#ensureClusterSizeConsistency()` method which check that the number of started nodes is the number of available nodes in the cluster. Disabling them temporary. Also, a new clientNode could be added (depends on seed). It adds a node more than expected. (cherry picked from commit bcc2cd5)
2014-06-15 17:28:15 -04:00
<dependency>
<groupId>org.hamcrest</groupId>
Depend on elasticsearch-parent To simplify plugins maintenance and provide more value in the future, we are starting to build an `elasticsearch-parent` project. This commit is the first step for this plugin to depend on this new `pom` maven project.
2015-01-02 15:30:46 -05:00
<artifactId>hamcrest-all</artifactId>
Fix tests When upgrading to elasticsearch 1.2.1 test framework, some tests are not working anymore because of `ElasticsearchIntegrationTest#ensureClusterSizeConsistency()` method which check that the number of started nodes is the number of available nodes in the cluster. Disabling them temporary. Also, a new clientNode could be added (depends on seed). It adds a node more than expected. (cherry picked from commit bcc2cd5)
2014-06-15 17:28:15 -04:00
</dependency>
<dependency>
Depend on elasticsearch-parent To simplify plugins maintenance and provide more value in the future, we are starting to build an `elasticsearch-parent` project. This commit is the first step for this plugin to depend on this new `pom` maven project.
2015-01-02 15:30:46 -05:00
<groupId>com.carrotsearch.randomizedtesting</groupId>
<artifactId>randomizedtesting-runner</artifactId>
Fix tests When upgrading to elasticsearch 1.2.1 test framework, some tests are not working anymore because of `ElasticsearchIntegrationTest#ensureClusterSizeConsistency()` method which check that the number of started nodes is the number of available nodes in the cluster. Disabling them temporary. Also, a new clientNode could be added (depends on seed). It adds a node more than expected. (cherry picked from commit bcc2cd5)
2014-06-15 17:28:15 -04:00
</dependency>
Move tests to elasticsearch test framework Closes #8.
2014-01-13 10:07:27 -05:00
<dependency>
<groupId>org.apache.lucene</groupId>
<artifactId>lucene-test-framework</artifactId>
</dependency>
Add cloud discovery for google compute engine Google Compute Engine VM discovery allows to use the google APIs to perform automatic discovery (similar to multicast in non hostile multicast environments). Here is a simple sample configuration: ```yaml cloud: gce: project_id: <your-google-project-id> zone: <your-zone> discovery: type: gce ``` How to start (short story) -------------------------- * Create Google Compute Engine instance * Install Elasticsearch * Install Google Compute Engine Cloud plugin * Modify `elasticsearch.yml` file * Start Elasticsearch Closes #1.
2013-06-28 03:45:02 -04:00
<dependency>
<groupId>org.elasticsearch</groupId>
<artifactId>elasticsearch</artifactId>
Depend on elasticsearch-parent To simplify plugins maintenance and provide more value in the future, we are starting to build an `elasticsearch-parent` project. This commit is the first step for this plugin to depend on this new `pom` maven project.
2015-01-02 15:30:46 -05:00
<scope>provided</scope>
Add cloud discovery for google compute engine Google Compute Engine VM discovery allows to use the google APIs to perform automatic discovery (similar to multicast in non hostile multicast environments). Here is a simple sample configuration: ```yaml cloud: gce: project_id: <your-google-project-id> zone: <your-zone> discovery: type: gce ``` How to start (short story) -------------------------- * Create Google Compute Engine instance * Install Elasticsearch * Install Google Compute Engine Cloud plugin * Modify `elasticsearch.yml` file * Start Elasticsearch Closes #1.
2013-06-28 03:45:02 -04:00
</dependency>
<!-- Google APIs -->
<dependency>
<groupId>com.google.api-client</groupId>
<artifactId>google-api-client</artifactId>
<version>${google.api.version}</version>
</dependency>
<dependency>
<groupId>com.google.http-client</groupId>
<artifactId>google-http-client-jackson2</artifactId>
<version>${google.api.version}</version>
</dependency>
<dependency>
<groupId>com.google.oauth-client</groupId>
<artifactId>google-oauth-client-jetty</artifactId>
<version>${google.api.version}</version>
</dependency>
<dependency>
<groupId>com.google.apis</groupId>
<artifactId>google-api-services-compute</artifactId>
<version>${google.gce.version}</version>
</dependency>
<!-- Tests -->
<dependency>
<groupId>log4j</groupId>
<artifactId>log4j</artifactId>
<scope>test</scope>
</dependency>
Fix tests When upgrading to elasticsearch 1.2.1 test framework, some tests are not working anymore because of `ElasticsearchIntegrationTest#ensureClusterSizeConsistency()` method which check that the number of started nodes is the number of available nodes in the cluster. Disabling them temporary. Also, a new clientNode could be added (depends on seed). It adds a node more than expected. (cherry picked from commit bcc2cd5)
2014-06-15 17:28:15 -04:00
Add cloud discovery for google compute engine Google Compute Engine VM discovery allows to use the google APIs to perform automatic discovery (similar to multicast in non hostile multicast environments). Here is a simple sample configuration: ```yaml cloud: gce: project_id: <your-google-project-id> zone: <your-zone> discovery: type: gce ``` How to start (short story) -------------------------- * Create Google Compute Engine instance * Install Elasticsearch * Install Google Compute Engine Cloud plugin * Modify `elasticsearch.yml` file * Start Elasticsearch Closes #1.
2013-06-28 03:45:02 -04:00
<dependency>
Move tests to elasticsearch test framework Closes #8.
2014-01-13 10:07:27 -05:00
<groupId>org.elasticsearch</groupId>
<artifactId>elasticsearch</artifactId>
<type>test-jar</type>
Add cloud discovery for google compute engine Google Compute Engine VM discovery allows to use the google APIs to perform automatic discovery (similar to multicast in non hostile multicast environments). Here is a simple sample configuration: ```yaml cloud: gce: project_id: <your-google-project-id> zone: <your-zone> discovery: type: gce ``` How to start (short story) -------------------------- * Create Google Compute Engine instance * Install Elasticsearch * Install Google Compute Engine Cloud plugin * Modify `elasticsearch.yml` file * Start Elasticsearch Closes #1.
2013-06-28 03:45:02 -04:00
</dependency>
</dependencies>
<build>
Trying to Mock GCE API for tests
2013-07-01 17:17:14 -04:00
<extensions>
<extension>
<groupId>org.kuali.maven.wagons</groupId>
<artifactId>maven-s3-wagon</artifactId>
<version>1.1.19</version>
</extension>
</extensions>
Add cloud discovery for google compute engine Google Compute Engine VM discovery allows to use the google APIs to perform automatic discovery (similar to multicast in non hostile multicast environments). Here is a simple sample configuration: ```yaml cloud: gce: project_id: <your-google-project-id> zone: <your-zone> discovery: type: gce ``` How to start (short story) -------------------------- * Create Google Compute Engine instance * Install Elasticsearch * Install Google Compute Engine Cloud plugin * Modify `elasticsearch.yml` file * Start Elasticsearch Closes #1.
2013-06-28 03:45:02 -04:00
<resources>
<resource>
<directory>src/main/resources</directory>
<filtering>true</filtering>
</resource>
</resources>
Changes after @imotov review.
2013-07-09 12:55:56 -04:00
<testResources>
<testResource>
<directory>src/test/resources</directory>
<filtering>true</filtering>
<includes>
Move tests to elasticsearch test framework Closes #16.
2014-03-12 07:03:27 -04:00
<include>plugin-test.properties</include>
Changes after @imotov review.
2013-07-09 12:55:56 -04:00
<include>elasticsearch.yml</include>
</includes>
</testResource>
<testResource>
<directory>src/test/resources</directory>
<filtering>false</filtering>
<includes>
<include>log4j.xml</include>
</includes>
</testResource>
</testResources>
Add cloud discovery for google compute engine Google Compute Engine VM discovery allows to use the google APIs to perform automatic discovery (similar to multicast in non hostile multicast environments). Here is a simple sample configuration: ```yaml cloud: gce: project_id: <your-google-project-id> zone: <your-zone> discovery: type: gce ``` How to start (short story) -------------------------- * Create Google Compute Engine instance * Install Elasticsearch * Install Google Compute Engine Cloud plugin * Modify `elasticsearch.yml` file * Start Elasticsearch Closes #1.
2013-06-28 03:45:02 -04:00
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
</plugin>
Move tests to elasticsearch test framework Closes #16.
2014-03-12 07:03:27 -04:00
<plugin>
<groupId>com.carrotsearch.randomizedtesting</groupId>
<artifactId>junit4-maven-plugin</artifactId>
<executions>
<execution>
<id>tests</id>
<phase>test</phase>
<goals>
<goal>junit4</goal>
</goals>
<configuration>
<heartbeat>20</heartbeat>
<jvmOutputAction>pipe,warn</jvmOutputAction>
<leaveTemporary>true</leaveTemporary>
<listeners>
<report-ant-xml mavenExtensions="true"
dir="${project.build.directory}/surefire-reports"/>
<report-text
showThrowable="true"
showStackTraces="true"
showOutput="${tests.output}"
showStatusOk="false"
showStatusError="true"
showStatusFailure="true"
showStatusIgnored="true"
showSuiteSummary="true"
timestamps="false"/>
<report-execution-times file="${basedir}/.local-execution-hints.log"/>
</listeners>
<assertions>
<enable/>
</assertions>
Run tests with only one JVM (cherry picked from commit d003f39)
2014-03-26 15:09:14 -04:00
<parallelism>1</parallelism>
Move tests to elasticsearch test framework Closes #16.
2014-03-12 07:03:27 -04:00
<balancers>
<execution-times>
<fileset dir="${basedir}" includes=".local-execution-hints.log"/>
</execution-times>
</balancers>
<includes>
<include>**/*Tests.class</include>
<include>**/*Test.class</include>
</includes>
<excludes>
<exclude>**/Abstract*.class</exclude>
<exclude>**/*StressTest.class</exclude>
</excludes>
<argLine>
${tests.jvm.argline}
</argLine>
<jvmArgs>
<param>-Xmx512m</param>
<param>-Xss256k</param>
<param>-XX:MaxDirectMemorySize=512m</param>
<param>-Des.logger.prefix=</param>
</jvmArgs>
<shuffleOnSlave>${tests.shuffle}</shuffleOnSlave>
<sysouts>${tests.verbose}</sysouts>
<seed>${tests.seed}</seed>
<haltOnFailure>${tests.failfast}</haltOnFailure>
<systemProperties>
<!-- RandomizedTesting library system properties -->
<tests.jvm.argline>${tests.jvm.argline}</tests.jvm.argline>
<tests.iters>${tests.iters}</tests.iters>
<tests.maxfailures>${tests.maxfailures}</tests.maxfailures>
<tests.failfast>${tests.failfast}</tests.failfast>
<tests.class>${tests.class}</tests.class>
<tests.method>${tests.method}</tests.method>
<tests.nightly>${tests.nightly}</tests.nightly>
<tests.badapples>${tests.badapples}</tests.badapples>
<tests.weekly>${tests.weekly}</tests.weekly>
<tests.slow>${tests.slow}</tests.slow>
<tests.gce>${tests.gce}</tests.gce>
Tests: refactor tests We need to simplify a bit our tests. Also, we need to mark as `@Ignore` tests as they break now due to some cluster controls after each test in elasticsearch test infra. See [org.elasticsearch.test.ElasticsearchIntegrationTest#ensureClusterSizeConsistency()](https://github.com/elasticsearch/elasticsearch/blob/v1.3.1/src/test/java/org/elasticsearch/test/ElasticsearchIntegrationTest.java#L974-L979) Closes #33.
2014-08-05 10:07:35 -04:00
<tests.config>${tests.config}</tests.config>
Move tests to elasticsearch test framework Closes #16.
2014-03-12 07:03:27 -04:00
<tests.awaitsfix>${tests.awaitsfix}</tests.awaitsfix>
<tests.slow>${tests.slow}</tests.slow>
<tests.timeoutSuite>${tests.timeoutSuite}</tests.timeoutSuite>
<tests.showSuccess>${tests.showSuccess}</tests.showSuccess>
<tests.integration>${tests.integration}</tests.integration>
<tests.cluster_seed>${tests.cluster_seed}</tests.cluster_seed>
<tests.client.ratio>${tests.client.ratio}</tests.client.ratio>
<es.logger.level>${es.logger.level}</es.logger.level>
<java.awt.headless>true</java.awt.headless>
</systemProperties>
</configuration>
</execution>
</executions>
</plugin>
Add cloud discovery for google compute engine Google Compute Engine VM discovery allows to use the google APIs to perform automatic discovery (similar to multicast in non hostile multicast environments). Here is a simple sample configuration: ```yaml cloud: gce: project_id: <your-google-project-id> zone: <your-zone> discovery: type: gce ``` How to start (short story) -------------------------- * Create Google Compute Engine instance * Install Elasticsearch * Install Google Compute Engine Cloud plugin * Modify `elasticsearch.yml` file * Start Elasticsearch Closes #1.
2013-06-28 03:45:02 -04:00
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-surefire-plugin</artifactId>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-source-plugin</artifactId>
</plugin>
<plugin>
Depend on elasticsearch-parent To simplify plugins maintenance and provide more value in the future, we are starting to build an `elasticsearch-parent` project. This commit is the first step for this plugin to depend on this new `pom` maven project.
2015-01-02 15:30:46 -05:00
<groupId>org.apache.maven.plugins</groupId>
Add cloud discovery for google compute engine Google Compute Engine VM discovery allows to use the google APIs to perform automatic discovery (similar to multicast in non hostile multicast environments). Here is a simple sample configuration: ```yaml cloud: gce: project_id: <your-google-project-id> zone: <your-zone> discovery: type: gce ``` How to start (short story) -------------------------- * Create Google Compute Engine instance * Install Elasticsearch * Install Google Compute Engine Cloud plugin * Modify `elasticsearch.yml` file * Start Elasticsearch Closes #1.
2013-06-28 03:45:02 -04:00
<artifactId>maven-assembly-plugin</artifactId>
<configuration>
<appendAssemblyId>false</appendAssemblyId>
<outputDirectory>${project.build.directory}/releases/</outputDirectory>
<descriptors>
<descriptor>${basedir}/src/main/assemblies/plugin.xml</descriptor>
</descriptors>
</configuration>
<executions>
<execution>
<phase>package</phase>
<goals>
<goal>single</goal>
</goals>
</execution>
</executions>
</plugin>
</plugins>
</build>
Depend on elasticsearch-parent To simplify plugins maintenance and provide more value in the future, we are starting to build an `elasticsearch-parent` project. This commit is the first step for this plugin to depend on this new `pom` maven project.
2015-01-02 15:30:46 -05:00
<repositories>
<repository>
<id>oss-snapshots</id>
<name>Sonatype OSS Snapshots</name>
<url>https://oss.sonatype.org/content/repositories/snapshots/</url>
</repository>
</repositories>
Add cloud discovery for google compute engine Google Compute Engine VM discovery allows to use the google APIs to perform automatic discovery (similar to multicast in non hostile multicast environments). Here is a simple sample configuration: ```yaml cloud: gce: project_id: <your-google-project-id> zone: <your-zone> discovery: type: gce ``` How to start (short story) -------------------------- * Create Google Compute Engine instance * Install Elasticsearch * Install Google Compute Engine Cloud plugin * Modify `elasticsearch.yml` file * Start Elasticsearch Closes #1.
2013-06-28 03:45:02 -04:00
</project>