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

1498 lines
76 KiB
XML
Raw Normal View History

initial pom
2011-12-05 18:05:44 -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>
create parent pom project from its original location
2015-06-05 07:12:05 -04:00
initial pom
2011-12-05 18:05:44 -05:00
<groupId>org.elasticsearch</groupId>
create parent pom project from its original location
2015-06-05 07:12:05 -04:00
<artifactId>elasticsearch-parent</artifactId>
updated the elasticsearch versioning format Moving to from `X.Y.Z.beta1`/`X.Y.Z.RC1` to `X.Y.Z-beta1`/`X.Y.Z-rc1`
2015-07-13 13:45:53 -04:00
<version>2.0.0-beta1-SNAPSHOT</version>
create parent pom project from its original location
2015-06-05 07:12:05 -04:00
<packaging>pom</packaging>
<name>Elasticsearch Parent POM</name>
<description>Elasticsearch Parent POM</description>
initial pom
2011-12-05 18:05:44 -05:00
<inceptionYear>2009</inceptionYear>
create parent pom project from its original location
2015-06-05 07:12:05 -04:00
<parent>
<groupId>org.sonatype.oss</groupId>
<artifactId>oss-parent</artifactId>
<version>7</version>
</parent>
initial pom
2011-12-05 18:05:44 -05:00
<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>
Upgrade to Lucene 4.7.1 * Removed XTermsFilter fixed in LUCENE-5502 * Switched back to automaton queries that caused failures due to LUCENE-5532 * Fixed Highlight test that has different results due to LUCENE-5538
2014-03-26 04:01:40 -04:00
initial pom
2011-12-05 18:05:44 -05:00
<scm>
create parent pom project from its original location
2015-06-05 07:12:05 -04:00
<connection>scm:git:git@github.com:elasticsearch/elasticsearch-parent.git</connection>
<developerConnection>scm:git:git@github.com:elasticsearch/elasticsearch-parent.git</developerConnection>
<url>http://github.com/elasticsearch/elasticsearch-parent</url>
initial pom
2011-12-05 18:05:44 -05:00
</scm>
<properties>
Add simple integ testing infra
2015-07-03 02:12:01 -04:00
<project.reporting.outputEncoding>UTF-8</project.reporting.outputEncoding>
create parent pom project from its original location
2015-06-05 07:12:05 -04:00
<!-- elasticsearch stack -->
appease maven warnings about using ${version} in pom
2015-07-09 16:38:15 -04:00
<elasticsearch.version>${project.version}</elasticsearch.version>
create parent pom project from its original location
2015-06-05 07:12:05 -04:00
<jvm.executable>${java.home}${file.separator}bin${file.separator}java</jvm.executable>
<maven.compiler.source>1.7</maven.compiler.source>
<maven.compiler.target>1.7</maven.compiler.target>
<!-- libraries -->
Upgrade to Lucene 5.2.1.
2015-06-15 04:51:05 -04:00
<lucene.version>5.2.1</lucene.version>
<lucene.maven.version>5.2.1</lucene.maven.version>
Use junit4 for running integration tests, too failsafe uses surefire, which sucks. It also mean integ tests act alien right now. I would rather have the consistency, e.g. things formatted the same way, running integ tests under security manager, etc.
2015-07-16 19:43:33 -04:00
<testframework.version>2.1.15</testframework.version>
create parent pom project from its original location
2015-06-05 07:12:05 -04:00
<jackson.version>2.5.3</jackson.version>
<slf4j.version>1.6.2</slf4j.version>
<log4j.version>1.2.17</log4j.version>
<!-- Build resources properties -->
<elasticsearch.tools.directory>${project.build.directory}/dev-tools</elasticsearch.tools.directory>
[BUILD] Run unshaded by default
2015-06-05 07:13:44 -04:00
<elasticsearch.thirdparty.config>unshaded</elasticsearch.thirdparty.config>
create parent pom project from its original location
2015-06-05 07:12:05 -04:00
<elasticsearch.license.header>${elasticsearch.tools.directory}/license-check/elasticsearch_license_header.txt</elasticsearch.license.header>
<elasticsearch.license.headerDefinition>${elasticsearch.tools.directory}/license-check/license_header_definition.xml</elasticsearch.license.headerDefinition>
protect logic under skipTests for stupid pom packaging
2015-07-16 20:49:16 -04:00
<elasticsearch.integ.antfile.default>${elasticsearch.tools.directory}/ant/integration-tests.xml</elasticsearch.integ.antfile.default>
<elasticsearch.integ.antfile>${elasticsearch.integ.antfile.default}</elasticsearch.integ.antfile>
create parent pom project from its original location
2015-06-05 07:12:05 -04:00
<!-- Test properties -->
<tests.jvms>auto</tests.jvms>
<tests.shuffle>true</tests.shuffle>
<tests.output>onerror</tests.output>
<tests.client.ratio></tests.client.ratio>
<tests.bwc.path>${project.basedir}/backwards</tests.bwc.path>
<tests.locale>random</tests.locale>
<tests.timezone>random</tests.timezone>
<tests.slow>false</tests.slow>
<es.logger.level>ERROR</es.logger.level>
<tests.heap.size>512m</tests.heap.size>
<tests.heapdump.path>${basedir}/logs/</tests.heapdump.path>
<tests.topn>5</tests.topn>
<execution.hint.file>.local-${elasticsearch.version}-execution-hints.log</execution.hint.file>
<tests.assertion.disabled>false</tests.assertion.disabled>
<tests.verbose>false</tests.verbose>
<tests.seed></tests.seed>
<tests.bwc></tests.bwc>
<tests.bwc.path></tests.bwc.path>
<tests.bwc.version></tests.bwc.version>
<tests.jvm.argline></tests.jvm.argline>
<tests.appendseed></tests.appendseed>
<tests.iters></tests.iters>
<tests.maxfailures></tests.maxfailures>
<tests.class></tests.class>
<tests.method></tests.method>
<tests.nightly></tests.nightly>
<tests.badapples></tests.badapples>
<tests.weekly></tests.weekly>
<tests.awaitsfix></tests.awaitsfix>
<tests.timeoutSuite></tests.timeoutSuite>
<tests.showSuccess></tests.showSuccess>
<tests.integration></tests.integration>
<tests.thirdparty></tests.thirdparty>
<tests.config></tests.config>
<tests.enable_mock_modules></tests.enable_mock_modules>
<tests.rest></tests.rest>
<tests.rest.suite></tests.rest.suite>
<tests.rest.blacklist></tests.rest.blacklist>
<tests.rest.spec></tests.rest.spec>
Get delete by query rest tests running
2015-07-06 15:13:50 -04:00
<tests.rest.load_packaged></tests.rest.load_packaged>
create parent pom project from its original location
2015-06-05 07:12:05 -04:00
<tests.network></tests.network>
<tests.cluster></tests.cluster>
<tests.filter></tests.filter>
<env.ES_TEST_LOCAL></env.ES_TEST_LOCAL>
<tests.security.manager>true</tests.security.manager>
<tests.compatibility></tests.compatibility>
<tests.ifNoTests>fail</tests.ifNoTests>
Add simple integ testing infra
2015-07-03 02:12:01 -04:00
<skip.unit.tests>${skipTests}</skip.unit.tests>
<skip.integ.tests>${skipTests}</skip.integ.tests>
isolate integ tests a little better. They are mostly just ES clients, but we can set tempdir and the usual stuff to contain them better.
2015-07-07 23:09:22 -04:00
<integ.scratch>${project.build.directory}/integ-tests</integ.scratch>
Refactor integration tests 1. tests don't have a bogus test dependency on zips anymore, instead we handle this in pre-integration-test. This reduces lots of confusion for e.g. mvn clean test. 2. refactor integ logic so that core/ and plugin/ share it. previously they were duplicates but the above change simplifies life. it also makes it easier for doing more interesting stuff
2015-07-14 23:37:04 -04:00
<integ.deps>${project.build.directory}/integ-deps</integ.deps>
isolate integ tests a little better. They are mostly just ES clients, but we can set tempdir and the usual stuff to contain them better.
2015-07-07 23:09:22 -04:00
<integ.temp>${integ.scratch}/temp</integ.temp>
Add a release profile to the parent pom.xml This commit adds a release profile that runs additional checks like: * check for `norelease` in the source * check for `AwaitsFix` annotations * deploys only if all reactor builds where successful * signs all artifacts with the GPG key provided (required for release) * builds the RPM together with the zip, tar.gz and .deb during package phase Note this is WIP of replacing major functionality of the release pythong script but won't work by itself.
2015-07-14 06:04:16 -04:00
<no.commit.pattern>\bno(n|)commit\b</no.commit.pattern>
initial pom
2011-12-05 18:05:44 -05:00
</properties>
add snapshot repo (so we know where to get elasticsearch-parent from if needed)
2015-05-23 00:27:28 -04:00
<repositories>
create parent pom project from its original location
2015-06-05 07:12:05 -04:00
<repository>
<id>elasticsearch-releases</id>
<url>http://maven.elasticsearch.org/releases</url>
<releases>
<enabled>true</enabled>
</releases>
<snapshots>
<enabled>false</enabled>
</snapshots>
</repository>
add snapshot repo (so we know where to get elasticsearch-parent from if needed)
2015-05-23 00:27:28 -04:00
<repository>
<id>oss-snapshots</id>
<name>Sonatype OSS Snapshots</name>
<url>https://oss.sonatype.org/content/repositories/snapshots/</url>
</repository>
</repositories>
create parent pom project from its original location
2015-06-05 07:12:05 -04:00
<dependencyManagement>
<dependencies>
<dependency>
<groupId>org.elasticsearch</groupId>
don't pull outdated/old packages.
2015-07-06 13:32:46 -04:00
<artifactId>elasticsearch-dev-tools</artifactId>
create parent pom project from its original location
2015-06-05 07:12:05 -04:00
<version>${elasticsearch.version}</version>
</dependency>
Update to shade plugin 2.2 to shade test artifact as well When we want to use test artifact in other projects, dependencies are not shaded as for core artifact. Issue opened in maven shade project: [MSHADE-158](http://jira.codehaus.org/browse/MSHADE-158) When using it in other projects, you basically need to change your `pom.xml` file: ```xml <dependency> <groupId>org.elasticsearch</groupId> <artifactId>elasticsearch</artifactId> <version>${elasticsearch.version}</version> <type>test-jar</type> <scope>test</scope> </dependency> ``` You can also define some properties: ```xml <properties> <tests.jvms>1</tests.jvms> <tests.shuffle>true</tests.shuffle> <tests.output>onerror</tests.output> <tests.client.ratio></tests.client.ratio> <es.logger.level>INFO</es.logger.level> </properties> ``` Closes #4266
2013-11-20 15:45:25 -05:00
create parent pom project from its original location
2015-06-05 07:12:05 -04:00
<dependency>
<groupId>com.carrotsearch.randomizedtesting</groupId>
<artifactId>randomizedtesting-runner</artifactId>
<version>${testframework.version}</version>
</dependency>
Upgrade to Netty 3.5.11 closes #2456
2012-12-02 16:29:49 -05:00
create parent pom project from its original location
2015-06-05 07:12:05 -04:00
<dependency>
<groupId>org.hamcrest</groupId>
<artifactId>hamcrest-all</artifactId>
<version>1.3</version>
</dependency>
initial pom
2011-12-05 18:05:44 -05:00
create parent pom project from its original location
2015-06-05 07:12:05 -04:00
<dependency>
<groupId>junit</groupId>
<artifactId>junit</artifactId>
<version>4.11</version>
</dependency>
finalize structure, tests pass
2011-12-05 19:42:25 -05:00
create parent pom project from its original location
2015-06-05 07:12:05 -04:00
<dependency>
<groupId>com.google.jimfs</groupId>
<artifactId>jimfs</artifactId>
<version>1.0</version>
</dependency>
Updating to HPPC-0.7.1 Close #11035
2015-05-07 06:02:33 -04:00
first stab at per-jar permissions for the scary stuff. unfortunately finds a crab in pluginmanager
2015-06-26 20:40:42 -04:00
<dependency>
<groupId>com.twitter</groupId>
<artifactId>jsr166e</artifactId>
<version>1.1.0</version>
</dependency>
create parent pom project from its original location
2015-06-05 07:12:05 -04:00
<dependency>
<groupId>org.apache.lucene</groupId>
<artifactId>lucene-test-framework</artifactId>
<version>${lucene.maven.version}</version>
Fail startup (and tests) on jar hell
2015-06-29 23:13:45 -04:00
<!-- we specify our own junit4 version -->
<exclusions>
<exclusion>
<groupId>com.carrotsearch.randomizedtesting</groupId>
<artifactId>junit4-ant</artifactId>
</exclusion>
</exclusions>
create parent pom project from its original location
2015-06-05 07:12:05 -04:00
</dependency>
finalize structure, tests pass
2011-12-05 19:42:25 -05:00
create parent pom project from its original location
2015-06-05 07:12:05 -04:00
<dependency>
<groupId>org.elasticsearch</groupId>
<artifactId>elasticsearch</artifactId>
<version>${elasticsearch.version}</version>
</dependency>
[maven] clean pom.xml In Maven parent project, in dependency management, we should only declare which versions of 3rd party jars we want to use but not force any scope. It makes then more obvious in modules what is exactly the scope of any dependency. For example, one could imagine importing `jimfs` as a `compile` dependency in another module/plugin with: ```xml <dependency> <groupId>com.google.jimfs</groupId> <artifactId>jimfs</artifactId> </dependency> ``` But it won't work as expected as the default maven `scope` should be `compile` but here it's `test` as defined in the parent project. So, if you want to use this lib for tests, you should simply define: ```xml <dependency> <groupId>com.google.jimfs</groupId> <artifactId>jimfs</artifactId> <scope>test</scope> </dependency> ``` We also remove `maven-s3-wagon` from gce plugin as it's not used.
2015-06-15 11:08:15 -04:00
create parent pom project from its original location
2015-06-05 07:12:05 -04:00
<dependency>
<groupId>org.elasticsearch</groupId>
<artifactId>elasticsearch</artifactId>
<version>${elasticsearch.version}</version>
<type>test-jar</type>
</dependency>
finalize structure, tests pass
2011-12-05 19:42:25 -05:00
integration tests need the zip
2015-07-06 12:29:30 -04:00
<dependency>
<groupId>org.elasticsearch</groupId>
<artifactId>elasticsearch</artifactId>
<version>${elasticsearch.version}</version>
<type>zip</type>
</dependency>
create parent pom project from its original location
2015-06-05 07:12:05 -04:00
<dependency>
<groupId>org.apache.httpcomponents</groupId>
<artifactId>httpclient</artifactId>
Upgrade AWS dependency to 1.10.0 This also apgrades JodaTime to 2.8.0.
2015-06-15 03:30:44 -04:00
<version>4.3.6</version>
create parent pom project from its original location
2015-06-05 07:12:05 -04:00
</dependency>
finalize structure, tests pass
2011-12-05 19:42:25 -05:00
create parent pom project from its original location
2015-06-05 07:12:05 -04:00
<dependency>
<groupId>org.apache.lucene</groupId>
<artifactId>lucene-core</artifactId>
<version>${lucene.maven.version}</version>
</dependency>
<dependency>
<groupId>org.apache.lucene</groupId>
<artifactId>lucene-backward-codecs</artifactId>
<version>${lucene.maven.version}</version>
</dependency>
<dependency>
<groupId>org.apache.lucene</groupId>
<artifactId>lucene-analyzers-common</artifactId>
<version>${lucene.maven.version}</version>
</dependency>
<dependency>
<groupId>org.apache.lucene</groupId>
<artifactId>lucene-queries</artifactId>
<version>${lucene.maven.version}</version>
<exclusions>
<exclusion>
<groupId>jakarta-regexp</groupId>
<artifactId>jakarta-regexp</artifactId>
</exclusion>
</exclusions>
</dependency>
<dependency>
<groupId>org.apache.lucene</groupId>
<artifactId>lucene-memory</artifactId>
<version>${lucene.maven.version}</version>
</dependency>
<dependency>
<groupId>org.apache.lucene</groupId>
<artifactId>lucene-highlighter</artifactId>
<version>${lucene.maven.version}</version>
</dependency>
<dependency>
<groupId>org.apache.lucene</groupId>
<artifactId>lucene-queryparser</artifactId>
<version>${lucene.maven.version}</version>
<exclusions>
<exclusion>
<groupId>jakarta-regexp</groupId>
<artifactId>jakarta-regexp</artifactId>
</exclusion>
</exclusions>
</dependency>
<dependency>
<groupId>org.apache.lucene</groupId>
<artifactId>lucene-suggest</artifactId>
<version>${lucene.maven.version}</version>
</dependency>
<dependency>
<groupId>org.apache.lucene</groupId>
<artifactId>lucene-join</artifactId>
<version>${lucene.maven.version}</version>
</dependency>
<!-- Lucene spatial, make sure when upgrading to work with latest version of jts/spatial4j dependencies -->
<dependency>
<groupId>org.apache.lucene</groupId>
<artifactId>lucene-spatial</artifactId>
<version>${lucene.maven.version}</version>
</dependency>
<dependency>
<groupId>org.apache.lucene</groupId>
<artifactId>lucene-expressions</artifactId>
<version>${lucene.maven.version}</version>
<optional>true</optional>
</dependency>
<dependency>
<groupId>com.spatial4j</groupId>
<artifactId>spatial4j</artifactId>
<version>0.4.1</version>
</dependency>
<dependency>
<groupId>com.vividsolutions</groupId>
<artifactId>jts</artifactId>
<version>1.13</version>
<exclusions>
<exclusion>
<groupId>xerces</groupId>
<artifactId>xercesImpl</artifactId>
</exclusion>
</exclusions>
</dependency>
<!-- needed for templating -->
<dependency>
<groupId>com.github.spullara.mustache.java</groupId>
<artifactId>compiler</artifactId>
<version>0.8.13</version>
</dependency>
finalize structure, tests pass
2011-12-05 19:42:25 -05:00
create parent pom project from its original location
2015-06-05 07:12:05 -04:00
<!-- Used in plugins -->
<dependency>
<groupId>org.apache.lucene</groupId>
<artifactId>lucene-analyzers-phonetic</artifactId>
<version>${lucene.maven.version}</version>
</dependency>
<dependency>
<groupId>org.apache.lucene</groupId>
<artifactId>lucene-analyzers-kuromoji</artifactId>
<version>${lucene.maven.version}</version>
</dependency>
<dependency>
<groupId>org.apache.lucene</groupId>
<artifactId>lucene-analyzers-stempel</artifactId>
<version>${lucene.maven.version}</version>
</dependency>
<dependency>
<groupId>org.apache.lucene</groupId>
<artifactId>lucene-analyzers-icu</artifactId>
<version>${lucene.maven.version}</version>
</dependency>
<dependency>
<groupId>org.apache.lucene</groupId>
<artifactId>lucene-analyzers-smartcn</artifactId>
<version>${lucene.maven.version}</version>
</dependency>
add CBOR data format support
2014-03-23 03:56:45 -04:00
create parent pom project from its original location
2015-06-05 07:12:05 -04:00
<!-- START: dependencies that might be shaded -->
<dependency>
<groupId>com.google.guava</groupId>
<artifactId>guava</artifactId>
<version>18.0</version>
</dependency>
abstract compression abstract the LZF compression into a compress package allowing for different implementation in the future
2012-06-18 22:07:11 -04:00
create parent pom project from its original location
2015-06-05 07:12:05 -04:00
<dependency>
<groupId>com.carrotsearch</groupId>
<artifactId>hppc</artifactId>
<version>0.7.1</version>
</dependency>
[BUILD] Shade t-digest.
2014-05-13 18:42:48 -04:00
create parent pom project from its original location
2015-06-05 07:12:05 -04:00
<dependency>
<groupId>joda-time</groupId>
<artifactId>joda-time</artifactId>
<!-- joda 2.0 moved to using volatile fields for datetime -->
<!-- When updating to a new version, make sure to update our copy of BaseDateTime -->
Upgrade AWS dependency to 1.10.0 This also apgrades JodaTime to 2.8.0.
2015-06-15 03:30:44 -04:00
<version>2.8</version>
create parent pom project from its original location
2015-06-05 07:12:05 -04:00
</dependency>
<dependency>
<groupId>org.joda</groupId>
<artifactId>joda-convert</artifactId>
<version>1.2</version>
</dependency>
Added a cli infrastructure CliTool is a base class for command-line interface tools (such as the plugin manager and potentially others). It supports the following: - single or multi command tool - help printing infrastructure (based on help files) - consistent mechanism of parsing arguments (based on commons-cli lib) - separation of argument parsing and command execution (for easier unit testing) - terminal abstraction (will use System.console() when available)
2014-08-02 11:16:27 -04:00
create parent pom project from its original location
2015-06-05 07:12:05 -04:00
<dependency>
<groupId>com.fasterxml.jackson.core</groupId>
<artifactId>jackson-core</artifactId>
<version>${jackson.version}</version>
</dependency>
Mappings: Make lookup structures immutable. This commit makes the lookup structures that are used for mappings immutable. When changes are required, a new instance is created while the current instance is left unmodified. This is done efficiently thanks to a hash table implementation based on a array hash trie, see org.elasticsearch.common.collect.CopyOnWriteHashMap. ManyMappingsBenchmark returns indexing times that are similar to the ones that can be observed in current master. Ultimately, I would like to see if we can make mappings completely immutable as well and updated atomically. This is not trivial however, eg. because of dynamic mappings. So here is a first baby step that should help move towards that direction. Close #7486
2014-08-20 08:29:09 -04:00
create parent pom project from its original location
2015-06-05 07:12:05 -04:00
<dependency>
<groupId>com.fasterxml.jackson.dataformat</groupId>
<artifactId>jackson-dataformat-smile</artifactId>
<version>${jackson.version}</version>
</dependency>
Added a cli infrastructure CliTool is a base class for command-line interface tools (such as the plugin manager and potentially others). It supports the following: - single or multi command tool - help printing infrastructure (based on help files) - consistent mechanism of parsing arguments (based on commons-cli lib) - separation of argument parsing and command execution (for easier unit testing) - terminal abstraction (will use System.console() when available)
2014-08-02 11:16:27 -04:00
create parent pom project from its original location
2015-06-05 07:12:05 -04:00
<dependency>
<groupId>com.fasterxml.jackson.dataformat</groupId>
<artifactId>jackson-dataformat-yaml</artifactId>
<version>${jackson.version}</version>
</dependency>
finalize structure, tests pass
2011-12-05 19:42:25 -05:00
create parent pom project from its original location
2015-06-05 07:12:05 -04:00
<dependency>
<groupId>com.fasterxml.jackson.dataformat</groupId>
<artifactId>jackson-dataformat-cbor</artifactId>
<version>${jackson.version}</version>
</dependency>
Add Groovy as a scripting language, add sandboxing for Groovy Sandboxes the groovy scripting language with multiple configurable whitelists: `script.groovy.sandbox.receiver_whitelist`: comma-separated list of string classes for objects that may have methods invoked. `script.groovy.sandbox.package_whitelist`: comma-separated list of packages under which new objects may be constructed. `script.groovy.sandbox.class_whitelist` comma-separated list of classes that are allowed to be constructed. As well as a method blacklist: `script.groovy.sandbox.method_blacklist`: comma-separated list of methods that are never allowed to be invoked, regardless of target object. The sandbox can be entirely disabled by setting: `script.groovy.sandbox.enabled: false`
2014-05-06 04:58:41 -04:00
create parent pom project from its original location
2015-06-05 07:12:05 -04:00
<dependency>
<groupId>io.netty</groupId>
<artifactId>netty</artifactId>
Update Netty to version 3.10.3.Final There a version mismatch between master (previously 3.10.0.Final) and 1.7 branch (3.10.3.Final)
2015-07-17 05:35:33 -04:00
<version>3.10.3.Final</version>
create parent pom project from its original location
2015-06-05 07:12:05 -04:00
</dependency>
initial pom
2011-12-05 18:05:44 -05:00
create parent pom project from its original location
2015-06-05 07:12:05 -04:00
<dependency>
<groupId>com.ning</groupId>
<artifactId>compress-lzf</artifactId>
<version>1.0.2</version>
</dependency>
Logging: Add log4j-extras dependency Close #7927
2014-09-30 12:35:55 -04:00
create parent pom project from its original location
2015-06-05 07:12:05 -04:00
<dependency>
<groupId>com.tdunning</groupId>
<artifactId>t-digest</artifactId>
<version>3.0</version>
</dependency>
finalize structure, tests pass
2011-12-05 19:42:25 -05:00
create parent pom project from its original location
2015-06-05 07:12:05 -04:00
<dependency>
<groupId>org.apache.commons</groupId>
<artifactId>commons-lang3</artifactId>
<version>3.3.2</version>
</dependency>
finalize structure, tests pass
2011-12-05 19:42:25 -05:00
create parent pom project from its original location
2015-06-05 07:12:05 -04:00
<dependency>
<groupId>commons-cli</groupId>
<artifactId>commons-cli</artifactId>
<version>1.2</version>
</dependency>
move to use sigar jar from maven central, which means that when using in the IDEA or running tests, sigar will not be enabled (since native files are not present), interim fix until we have a better one
2012-02-14 05:49:15 -05:00
create parent pom project from its original location
2015-06-05 07:12:05 -04:00
<!-- END: dependencies that might be shaded -->
initial pom
2011-12-05 18:05:44 -05:00
create parent pom project from its original location
2015-06-05 07:12:05 -04:00
<dependency>
<groupId>org.codehaus.groovy</groupId>
<artifactId>groovy-all</artifactId>
upgraded groovy from 2.4.0 to 2.4.4
2015-07-16 07:56:32 -04:00
<version>2.4.4</version>
create parent pom project from its original location
2015-06-05 07:12:05 -04:00
<classifier>indy</classifier>
</dependency>
finalize structure, tests pass
2011-12-05 19:42:25 -05:00
create parent pom project from its original location
2015-06-05 07:12:05 -04:00
<dependency>
<groupId>log4j</groupId>
<artifactId>log4j</artifactId>
<version>${log4j.version}</version>
</dependency>
Add properties files to configure startup and installation scripts Many scripts are used to start/stop and install/uninstall elasticsearch. These scripts share a lot of configuration properties like directory paths, max value for a setting, default user etc. Most of the values are identical but some of them are different depending of the platform (Debian-based or Redhat-based OS), depending of the way elasticsearch is started (shell script, systemd, sysv-init...) or the way it is installed (zip, rpm, deb...). Today the values are duplicated in multiple places, making it difficult to maintain the scripts or to update a value. This pull request make this more uniform: values used in scripts must be defined in a common packaging.properties file. Each value can be overridden in another specific packaging.properties file for Debian or Redhat. All startup and installation scripts are filtered with the common then the custom packaging.properties files before being packaged as a zip/tar.gz/rpm/dpkf archive.
2015-03-30 09:58:34 -04:00
create parent pom project from its original location
2015-06-05 07:12:05 -04:00
<dependency>
<groupId>log4j</groupId>
<artifactId>apache-log4j-extras</artifactId>
<version>${log4j.version}</version>
</dependency>
finalize structure, tests pass
2011-12-05 19:42:25 -05:00
create parent pom project from its original location
2015-06-05 07:12:05 -04:00
<dependency>
<groupId>org.slf4j</groupId>
<artifactId>slf4j-api</artifactId>
<version>${slf4j.version}</version>
</dependency>
finalize structure, tests pass
2011-12-05 19:42:25 -05:00
create parent pom project from its original location
2015-06-05 07:12:05 -04:00
<dependency>
<groupId>org.slf4j</groupId>
<artifactId>slf4j-log4j12</artifactId>
<version>${slf4j.version}</version>
</dependency>
<dependency>
<groupId>net.java.dev.jna</groupId>
<artifactId>jna</artifactId>
<version>4.1.0</version>
<optional>true</optional>
</dependency>
<!-- For coverage analysis -->
<dependency>
<groupId>org.jacoco</groupId>
<artifactId>org.jacoco.agent</artifactId>
<classifier>runtime</classifier>
<version>0.6.4.201312101107</version>
</dependency>
</dependencies>
</dependencyManagement>
<build>
<plugins>
enable enforcer plugin
2015-07-14 13:41:54 -04:00
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-enforcer-plugin</artifactId>
</plugin>
create parent pom project from its original location
2015-06-05 07:12:05 -04:00
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
</plugin>
Refactor integration tests 1. tests don't have a bogus test dependency on zips anymore, instead we handle this in pre-integration-test. This reduces lots of confusion for e.g. mvn clean test. 2. refactor integ logic so that core/ and plugin/ share it. previously they were duplicates but the above change simplifies life. it also makes it easier for doing more interesting stuff
2015-07-14 23:37:04 -04:00
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-dependency-plugin</artifactId>
</plugin>
create parent pom project from its original location
2015-06-05 07:12:05 -04:00
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>buildnumber-maven-plugin</artifactId>
</plugin>
<plugin>
<groupId>com.carrotsearch.randomizedtesting</groupId>
<artifactId>junit4-maven-plugin</artifactId>
</plugin>
Use junit4 for running integration tests, too failsafe uses surefire, which sucks. It also mean integ tests act alien right now. I would rather have the consistency, e.g. things formatted the same way, running integ tests under security manager, etc.
2015-07-16 19:43:33 -04:00
<!-- we only use failsafe's "verify" right now -->
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-failsafe-plugin</artifactId>
</plugin>
create parent pom project from its original location
2015-06-05 07:12:05 -04:00
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-source-plugin</artifactId>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-remote-resources-plugin</artifactId>
</plugin>
<plugin>
<groupId>de.thetaphi</groupId>
<artifactId>forbiddenapis</artifactId>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-antrun-plugin</artifactId>
</plugin>
</plugins>
<pluginManagement>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-assembly-plugin</artifactId>
[maven] update maven-assembly-plugin to 2.5.5 ```xml <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-assembly-plugin</artifactId> <version>2.5.5</version> </plugin> ``` ## Release Notes - Maven Assembly Plugin - Version 2.5.5 * Bug - [MASSEMBLY-767] - Schema missing from the web site - [MASSEMBLY-768] - JarInputStream unable to find manifest created by version 2.5.4 - [MASSEMBLY-769] - ZIP fileMode permissions not properly set with dependencySet and unpackOptions
2015-06-05 13:17:21 -04:00
<version>2.5.5</version>
create parent pom project from its original location
2015-06-05 07:12:05 -04:00
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-clean-plugin</artifactId>
<version>2.6.1</version>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-deploy-plugin</artifactId>
<version>2.8.2</version>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-gpg-plugin</artifactId>
<version>1.6</version>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-enforcer-plugin</artifactId>
<version>1.4</version>
<executions>
<execution>
<id>enforce-versions</id>
<goals>
<goal>enforce</goal>
</goals>
<configuration>
<rules>
<requireJavaVersion>
<version>[${maven.compiler.source},)</version>
</requireJavaVersion>
</rules>
</configuration>
</execution>
Use enforcer:display-info to print version info Currently this is done with ant tasks, but this is simpler and designed for this purpose.
2015-07-14 14:48:20 -04:00
<execution>
<id>print-versions</id>
<phase>validate</phase>
<goals>
<goal>display-info</goal>
</goals>
</execution>
create parent pom project from its original location
2015-06-05 07:12:05 -04:00
</executions>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<version>3.3</version>
<configuration>
<fork>true</fork>
<maxmem>512m</maxmem>
<!-- REMOVE WHEN UPGRADE:
see https://jira.codehaus.org/browse/MCOMPILER-209 it's a bug where
incremental compilation doesn't work unless it's set to false causeing
recompilation of the entire codebase each time without any changes. Should
be fixed in version > 3.1
-->
<useIncrementalCompilation>false</useIncrementalCompilation>
<compilerArgs>
<arg>-XDignore.symbol.file</arg>
</compilerArgs>
</configuration>
</plugin>
<plugin>
<groupId>com.carrotsearch.randomizedtesting</groupId>
<artifactId>junit4-maven-plugin</artifactId>
<version>${testframework.version}</version>
Use junit4 for running integration tests, too failsafe uses surefire, which sucks. It also mean integ tests act alien right now. I would rather have the consistency, e.g. things formatted the same way, running integ tests under security manager, etc.
2015-07-16 19:43:33 -04:00
<!-- general test configuration, used for both unit and integ tests -->
<configuration>
<jvm>${jvm.executable}</jvm>
<argLine>${tests.jvm.argline}</argLine>
<heartbeat>10</heartbeat>
<jvmOutputAction>warn</jvmOutputAction>
<leaveTemporary>true</leaveTemporary>
<parallelism>${tests.jvms}</parallelism>
<ifNoTests>${tests.ifNoTests}</ifNoTests>
<assertions enableSystemAssertions="true">
<enable/>
<disable package="${tests.assertion.disabled}"/>
<!-- pass org.elasticsearch to run without assertions -->
</assertions>
<balancers>
<execution-times>
<fileset dir="${basedir}" includes="${execution.hint.file}"/>
</execution-times>
</balancers>
<jvmArgs>
<param>-Xmx${tests.heap.size}</param>
<param>-Xms${tests.heap.size}</param>
<param>${java.permGenSpace}</param>
<param>-XX:MaxDirectMemorySize=512m</param>
<param>-Des.logger.prefix=</param>
<param>-XX:+HeapDumpOnOutOfMemoryError</param>
<param>-XX:HeapDumpPath=${tests.heapdump.path}</param>
</jvmArgs>
<shuffleOnSlave>${tests.shuffle}</shuffleOnSlave>
<sysouts>${tests.verbose}</sysouts>
<seed>${tests.seed}</seed>
<!-- enforce unique suite names, or reporting stuff can be screwed up -->
<uniqueSuiteNames>true</uniqueSuiteNames>
<systemProperties>
<!-- we use './temp' since this is per JVM and tests are forbidden from writing to CWD -->
<java.io.tmpdir>./temp</java.io.tmpdir>
<!-- RandomizedTesting library system properties -->
<tests.bwc>${tests.bwc}</tests.bwc>
<tests.bwc.path>${tests.bwc.path}</tests.bwc.path>
<tests.bwc.version>${tests.bwc.version}</tests.bwc.version>
<tests.jvm.argline>${tests.jvm.argline}</tests.jvm.argline>
<tests.appendseed>${tests.appendseed}</tests.appendseed>
<tests.cluster>${tests.cluster}</tests.cluster>
<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.verbose>${tests.verbose}</tests.verbose>
<tests.badapples>${tests.badapples}</tests.badapples>
<tests.weekly>${tests.weekly}</tests.weekly>
<haltOnFailure>${tests.failfast}</haltOnFailure>
<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.thirdparty>${tests.thirdparty}</tests.thirdparty>
<tests.config>${tests.config}</tests.config>
<tests.client.ratio>${tests.client.ratio}</tests.client.ratio>
<tests.enable_mock_modules>${tests.enable_mock_modules}</tests.enable_mock_modules>
<tests.assertion.disabled>${tests.assertion.disabled}</tests.assertion.disabled>
<tests.rest>${tests.rest}</tests.rest>
<tests.rest.suite>${tests.rest.suite}</tests.rest.suite>
<tests.rest.blacklist>${tests.rest.blacklist}</tests.rest.blacklist>
<tests.rest.spec>${tests.rest.spec}</tests.rest.spec>
<tests.network>${tests.network}</tests.network>
<tests.heap.size>${tests.heap.size}</tests.heap.size>
<tests.filter>${tests.filter}</tests.filter>
<tests.version>${elasticsearch.version}</tests.version>
<tests.locale>${tests.locale}</tests.locale>
<tests.rest.load_packaged>${tests.rest.load_packaged}</tests.rest.load_packaged>
<tests.timezone>${tests.timezone}</tests.timezone>
<es.node.local>${env.ES_TEST_LOCAL}</es.node.local>
<es.node.mode>${es.node.mode}</es.node.mode>
<es.logger.level>${es.logger.level}</es.logger.level>
<tests.security.manager>${tests.security.manager}</tests.security.manager>
<tests.compatibility>${tests.compatibility}</tests.compatibility>
<java.awt.headless>true</java.awt.headless>
<!-- true if we are running tests from maven (as opposed to IDE, etc).
allows us to assert certain things work, like libsigar -->
<tests.maven>true</tests.maven>
</systemProperties>
<listeners>
<report-text
showThrowable="true"
showStackTraces="true"
showOutput="${tests.output}"
showStatusOk="false"
showStatusError="true"
showStatusFailure="true"
showStatusIgnored="true"
showSuiteSummary="true"
timestamps="false">
<filtertrace>
<!-- custom filters: we carefully only omit test infra noise here -->
<containsstring contains=".SlaveMain." />
<containsregex pattern="^(\s+at )(org\.junit\.)" />
<!-- also includes anonymous classes inside these two: -->
<containsregex pattern="^(\s+at )(com\.carrotsearch\.randomizedtesting.RandomizedRunner)" />
<containsregex pattern="^(\s+at )(com\.carrotsearch\.randomizedtesting.ThreadLeakControl)" />
<containsregex pattern="^(\s+at )(com\.carrotsearch\.randomizedtesting.rules\.)" />
<containsregex pattern="^(\s+at )(org\.apache\.lucene.util\.TestRule)" />
<containsregex pattern="^(\s+at )(org\.apache\.lucene.util\.AbstractBeforeAfterRule)" />
</filtertrace>
</report-text>
move tophints configuration to the correct place
2015-07-16 22:49:30 -04:00
<report-execution-times historyLength="20" file="${basedir}/${execution.hint.file}"/>
Use junit4 for running integration tests, too failsafe uses surefire, which sucks. It also mean integ tests act alien right now. I would rather have the consistency, e.g. things formatted the same way, running integ tests under security manager, etc.
2015-07-16 19:43:33 -04:00
</listeners>
</configuration>
create parent pom project from its original location
2015-06-05 07:12:05 -04:00
<executions>
<execution>
<id>tests</id>
<phase>test</phase>
<goals>
<goal>junit4</goal>
</goals>
<configuration>
Add simple integ testing infra
2015-07-03 02:12:01 -04:00
<skipTests>${skip.unit.tests}</skipTests>
create parent pom project from its original location
2015-06-05 07:12:05 -04:00
<listeners>
<report-ant-xml mavenExtensions="true"
dir="${project.build.directory}/surefire-reports"/>
</listeners>
<includes>
<include>**/*Tests.class</include>
<include>**/*Test.class</include>
</includes>
<excludes>
<exclude>**/Abstract*.class</exclude>
<exclude>**/*StressTest.class</exclude>
</excludes>
Use junit4 for running integration tests, too failsafe uses surefire, which sucks. It also mean integ tests act alien right now. I would rather have the consistency, e.g. things formatted the same way, running integ tests under security manager, etc.
2015-07-16 19:43:33 -04:00
</configuration>
</execution>
<execution>
<id>integ-tests</id>
<phase>integration-test</phase>
<goals>
<goal>junit4</goal>
</goals>
<configuration>
<haltOnFailure>false</haltOnFailure>
<skipTests>${skip.integ.tests}</skipTests>
<listeners>
<report-ant-xml
mavenExtensions="true"
summaryFile="${project.build.directory}/failsafe-reports/failsafe-summary-buggy.xml"
dir="${project.build.directory}/failsafe-reports"/>
</listeners>
<!-- currently only 1 cpu works, because integ tests don't make "unique" test directories? -->
<parallelism>1</parallelism>
<includes>
<include>**/*IT.class</include>
</includes>
create parent pom project from its original location
2015-06-05 07:12:05 -04:00
<systemProperties>
Use junit4 for running integration tests, too failsafe uses surefire, which sucks. It also mean integ tests act alien right now. I would rather have the consistency, e.g. things formatted the same way, running integ tests under security manager, etc.
2015-07-16 19:43:33 -04:00
<!-- integ tests are typically slow! -->
<tests.slow>true</tests.slow>
<!-- use external cluster -->
<tests.cluster>127.0.0.1:9300</tests.cluster>
fix REPRODUCE WITH for integration tests
2015-07-16 21:45:20 -04:00
<!-- let framework know we are running integ tests, for correct 'reproduce with' line -->
<tests.verify.phase>true</tests.verify.phase>
create parent pom project from its original location
2015-06-05 07:12:05 -04:00
</systemProperties>
</configuration>
</execution>
</executions>
</plugin>
<!-- disable surefire, we use junit4 -->
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-surefire-plugin</artifactId>
<version>2.18.1</version>
<configuration>
<skip>true</skip>
</configuration>
</plugin>
Add simple integ testing infra
2015-07-03 02:12:01 -04:00
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-failsafe-plugin</artifactId>
<version>2.18.1</version>
Don't try to verify if we are skipping integ tests (e.g. don't have any, explicitly disabled, etc)
2015-07-16 22:12:00 -04:00
<configuration>
<skip>${skip.integ.tests}</skip>
</configuration>
Add simple integ testing infra
2015-07-03 02:12:01 -04:00
<executions>
use external test cluster for integration tests
2015-07-03 12:20:35 -04:00
<execution>
<id>verify</id>
<goals>
Add simple integ testing infra
2015-07-03 02:12:01 -04:00
<goal>verify</goal>
</goals>
</execution>
</executions>
</plugin>
create parent pom project from its original location
2015-06-05 07:12:05 -04:00
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-source-plugin</artifactId>
<version>2.4</version>
<executions>
<execution>
<id>attach-sources</id>
<goals>
<goal>jar</goal>
</goals>
</execution>
</executions>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-remote-resources-plugin</artifactId>
<version>1.5</version>
<configuration>
<resourceBundles>
don't pull outdated/old packages.
2015-07-06 13:32:46 -04:00
<resourceBundle>org.elasticsearch:elasticsearch-dev-tools:${elasticsearch.version}</resourceBundle>
<resourceBundle>org.elasticsearch:elasticsearch-rest-api-spec:${elasticsearch.version}</resourceBundle>
create parent pom project from its original location
2015-06-05 07:12:05 -04:00
</resourceBundles>
<outputDirectory>${elasticsearch.tools.directory}</outputDirectory>
<!-- don't include dev-tools in artifacts -->
<attachToMain>false</attachToMain>
<attachToTest>false</attachToTest>
</configuration>
<executions>
<execution>
<goals>
<goal>process</goal>
</goals>
</execution>
</executions>
</plugin>
<plugin>
<groupId>de.thetaphi</groupId>
<artifactId>forbiddenapis</artifactId>
<version>1.8</version>
<executions>
<execution>
<id>check-forbidden-apis</id>
<configuration>
<targetVersion>${maven.compiler.target}</targetVersion>
<!-- disallow undocumented classes like sun.misc.Unsafe: -->
<internalRuntimeForbidden>true</internalRuntimeForbidden>
<!-- if the used Java version is too new, don't fail, just do nothing: -->
<failOnUnsupportedJava>false</failOnUnsupportedJava>
<bundledSignatures>
<!-- This will automatically choose the right signatures based on 'targetVersion': -->
<bundledSignature>jdk-unsafe</bundledSignature>
<bundledSignature>jdk-deprecated</bundledSignature>
<bundledSignature>jdk-system-out</bundledSignature>
</bundledSignatures>
<signaturesFiles>
<signaturesFile>${elasticsearch.tools.directory}/forbidden/core-signatures.txt</signaturesFile>
<signaturesFile>${elasticsearch.tools.directory}/forbidden/all-signatures.txt</signaturesFile>
<signaturesFile>${elasticsearch.tools.directory}/forbidden/third-party-${elasticsearch.thirdparty.config}-signatures.txt</signaturesFile>
</signaturesFiles>
<signatures>${forbidden.signatures}</signatures>
<suppressAnnotations><annotation>**.SuppressForbidden</annotation></suppressAnnotations>
</configuration>
<phase>compile</phase>
<goals>
<goal>check</goal>
</goals>
</execution>
<execution>
<id>check-forbidden-test-apis</id>
<configuration>
<targetVersion>${maven.compiler.target}</targetVersion>
<!-- disallow undocumented classes like sun.misc.Unsafe: -->
<internalRuntimeForbidden>true</internalRuntimeForbidden>
<!-- if the used Java version is too new, don't fail, just do nothing: -->
<failOnUnsupportedJava>false</failOnUnsupportedJava>
<bundledSignatures>
<!-- This will automatically choose the right signatures based on 'targetVersion': -->
<bundledSignature>jdk-unsafe</bundledSignature>
<bundledSignature>jdk-deprecated</bundledSignature>
</bundledSignatures>
<signaturesFiles>
<signaturesFile>${elasticsearch.tools.directory}/forbidden/test-signatures.txt</signaturesFile>
<signaturesFile>${elasticsearch.tools.directory}/forbidden/all-signatures.txt</signaturesFile>
</signaturesFiles>
<signatures>${forbidden.test.signatures}</signatures>
<suppressAnnotations><annotation>**.SuppressForbidden</annotation></suppressAnnotations>
</configuration>
<phase>test-compile</phase>
<goals>
<goal>testCheck</goal>
</goals>
</execution>
</executions>
</plugin>
<plugin>
<!-- We just declare which plugin version to use. Each project can have then its own settings -->
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-shade-plugin</artifactId>
[build] update maven-shade-plugin to 2.4 ## Release Notes - Apache Maven Shade - Version 2.4 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317921&version=12331393 ### Bugs: * [MSHADE-155] - dependency-reduced-pom should use shadedArtifactId * [MSHADE-169] - Typos in warning message * [MSHADE-172] - "java.lang.ArithmeticException: / by zero" in MinijarFilter * [MSHADE-174] - Unable to shade Java 8 jarfiles with static interface methods using minimizeJar * [MSHADE-183] - Getting "Error creating shaded jar: java.util.jar.Attributes cannot be cast to java.lang.String" error when using ManifestResourceTransformer with Maven 3.2.5 * [MSHADE-185] - systemPath content is interpolated for system dependencies ### Improvements: * [MSHADE-177] - MavenProject/MavenSession Injection as a paremeter instead as a component. * [MSHADE-178] - Removing plexus-container-default dependency * [MSHADE-179] - Fix RAT Report * [MSHADE-180] - Upgrade plexus-utils to 3.0.18 * [MSHADE-188] - Upgrade maven-dependency-tree to 2.2 * [MSHADE-191] - Upgrade plexus-utils to 3.0.22 * [MSHADE-192] - Upgrade maven-invoker to 1.10 * [MSHADE-193] - Upgrade to fluido skin 1.4.0
2015-06-12 07:56:35 -04:00
<version>2.4</version>
create parent pom project from its original location
2015-06-05 07:12:05 -04:00
</plugin>
<plugin>
<!-- We just declare which plugin version to use. Each project can have then its own settings -->
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-resources-plugin</artifactId>
<version>2.7</version>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-site-plugin</artifactId>
<version>3.4</version>
<configuration>
<siteDirectory>${elasticsearch.tools.directory}/site</siteDirectory>
</configuration>
</plugin>
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>buildnumber-maven-plugin</artifactId>
<version>1.3</version>
<executions>
<execution>
<phase>validate</phase>
<goals>
<goal>create</goal>
</goals>
</execution>
</executions>
<configuration>
<doCheck>false</doCheck>
<doUpdate>false</doUpdate>
</configuration>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-dependency-plugin</artifactId>
<version>2.10</version>
Refactor integration tests 1. tests don't have a bogus test dependency on zips anymore, instead we handle this in pre-integration-test. This reduces lots of confusion for e.g. mvn clean test. 2. refactor integ logic so that core/ and plugin/ share it. previously they were duplicates but the above change simplifies life. it also makes it easier for doing more interesting stuff
2015-07-14 23:37:04 -04:00
<executions>
<execution>
<id>integ-setup-dependencies</id>
<phase>pre-integration-test</phase>
<goals>
<goal>copy</goal>
</goals>
<configuration>
<artifactItems>
<artifactItem>
<groupId>org.elasticsearch</groupId>
<artifactId>elasticsearch</artifactId>
<version>${elasticsearch.version}</version>
<type>zip</type>
<overWrite>true</overWrite>
</artifactItem>
</artifactItems>
integration tests should use the baseVersion when copying artifacts
2015-07-15 15:25:43 -04:00
<useBaseVersion>true</useBaseVersion>
Refactor integration tests 1. tests don't have a bogus test dependency on zips anymore, instead we handle this in pre-integration-test. This reduces lots of confusion for e.g. mvn clean test. 2. refactor integ logic so that core/ and plugin/ share it. previously they were duplicates but the above change simplifies life. it also makes it easier for doing more interesting stuff
2015-07-14 23:37:04 -04:00
<outputDirectory>${integ.deps}</outputDirectory>
</configuration>
</execution>
</executions>
create parent pom project from its original location
2015-06-05 07:12:05 -04:00
</plugin>
<plugin>
<!-- We just declare which plugin version to use. Each project can have then its own settings -->
<!-- some infos https://github.com/tcurdt/jdeb/blob/master/docs/maven.md -->
<groupId>org.vafer</groupId>
<artifactId>jdeb</artifactId>
<version>1.3</version>
</plugin>
<plugin>
<!-- We just declare which plugin version to use. Each project can have then its own settings -->
<groupId>org.codehaus.mojo</groupId>
<artifactId>rpm-maven-plugin</artifactId>
<version>2.1.2</version>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-jar-plugin</artifactId>
<version>2.5</version>
<configuration>
<archive>
<manifest>
<addDefaultImplementationEntries>true</addDefaultImplementationEntries>
</manifest>
Ensure shaded jar has manifest too
2015-05-23 08:37:50 -04:00
<manifestEntries>
create parent pom project from its original location
2015-06-05 07:12:05 -04:00
<X-Build-Branch>${scmBranch}</X-Build-Branch>
<X-Build-Number>${buildNumber}</X-Build-Number>
<X-Build-Time>${timestamp}</X-Build-Time>
<X-Compile-Elasticsearch-Version>${elasticsearch.version}</X-Compile-Elasticsearch-Version>
<X-Compile-Lucene-Version>${lucene.version}</X-Compile-Lucene-Version>
<X-Compile-Source-JDK>${maven.compiler.source}</X-Compile-Source-JDK>
<X-Compile-Target-JDK>${maven.compiler.target}</X-Compile-Target-JDK>
Ensure shaded jar has manifest too
2015-05-23 08:37:50 -04:00
</manifestEntries>
create parent pom project from its original location
2015-06-05 07:12:05 -04:00
</archive>
</configuration>
</plugin>
Add properties files to configure startup and installation scripts Many scripts are used to start/stop and install/uninstall elasticsearch. These scripts share a lot of configuration properties like directory paths, max value for a setting, default user etc. Most of the values are identical but some of them are different depending of the platform (Debian-based or Redhat-based OS), depending of the way elasticsearch is started (shell script, systemd, sysv-init...) or the way it is installed (zip, rpm, deb...). Today the values are duplicated in multiple places, making it difficult to maintain the scripts or to update a value. This pull request make this more uniform: values used in scripts must be defined in a common packaging.properties file. Each value can be overridden in another specific packaging.properties file for Debian or Redhat. All startup and installation scripts are filtered with the common then the custom packaging.properties files before being packaged as a zip/tar.gz/rpm/dpkf archive.
2015-03-30 09:58:34 -04:00
create parent pom project from its original location
2015-06-05 07:12:05 -04:00
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>license-maven-plugin</artifactId>
<version>1.8</version>
</plugin>
moving debian package to maven
2011-12-08 03:48:00 -05:00
create parent pom project from its original location
2015-06-05 07:12:05 -04:00
<plugin>
<groupId>com.mycila</groupId>
<artifactId>license-maven-plugin</artifactId>
<version>2.5</version>
<configuration>
<header>${elasticsearch.license.header}</header>
<headerDefinitions>
<headerDefinition>${elasticsearch.license.headerDefinition}</headerDefinition>
</headerDefinitions>
<includes>
<include>src/main/java/org/elasticsearch/**/*.java</include>
<include>src/test/java/org/elasticsearch/**/*.java</include>
</includes>
</configuration>
<executions>
<execution>
<id>check-license-headers</id>
<phase>compile</phase>
<goals>
<goal>check</goal>
</goals>
</execution>
</executions>
</plugin>
Add properties files to configure startup and installation scripts Many scripts are used to start/stop and install/uninstall elasticsearch. These scripts share a lot of configuration properties like directory paths, max value for a setting, default user etc. Most of the values are identical but some of them are different depending of the platform (Debian-based or Redhat-based OS), depending of the way elasticsearch is started (shell script, systemd, sysv-init...) or the way it is installed (zip, rpm, deb...). Today the values are duplicated in multiple places, making it difficult to maintain the scripts or to update a value. This pull request make this more uniform: values used in scripts must be defined in a common packaging.properties file. Each value can be overridden in another specific packaging.properties file for Debian or Redhat. All startup and installation scripts are filtered with the common then the custom packaging.properties files before being packaged as a zip/tar.gz/rpm/dpkf archive.
2015-03-30 09:58:34 -04:00
create parent pom project from its original location
2015-06-05 07:12:05 -04:00
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-eclipse-plugin</artifactId>
<version>2.9</version>
<configuration>
<buildOutputDirectory>eclipse-build</buildOutputDirectory>
<downloadSources>true</downloadSources>
Adds eclipse settings files to set correct encoding and complier preferences This is done in the maven-eclipse-plugin so now all eclipse files are generated by mV eclipse:eclipse and can safely be ignored
2015-06-08 09:39:17 -04:00
<additionalConfig>
<file>
<name>.settings/org.eclipse.core.resources.prefs</name>
<content>
<![CDATA[eclipse.preferences.version=1
encoding//src/main/java=UTF-8
encoding//src/main/resources=UTF-8
encoding//src/test/java=UTF-8
encoding//src/test/resources=UTF-8
encoding/<project>=UTF-8
]]>
</content>
</file>
<file>
<name>.settings/org.eclipse.jdt.core.prefs</name>
<content>
<![CDATA[eclipse.preferences.version=1
org.eclipse.jdt.core.compiler.annotation.inheritNullAnnotations=enabled
org.eclipse.jdt.core.compiler.annotation.missingNonNullByDefaultAnnotation=ignore
org.eclipse.jdt.core.compiler.annotation.nullable=org.elasticsearch.common.Nullable
org.eclipse.jdt.core.compiler.annotation.nullanalysis=enabled
org.eclipse.jdt.core.compiler.codegen.targetPlatform=1.7
org.eclipse.jdt.core.compiler.compliance=1.7
org.eclipse.jdt.core.compiler.problem.forbiddenReference=warning
org.eclipse.jdt.core.compiler.problem.nonnullParameterAnnotationDropped=warning
org.eclipse.jdt.core.compiler.problem.nullAnnotationInferenceConflict=warning
org.eclipse.jdt.core.compiler.problem.nullReference=warning
org.eclipse.jdt.core.compiler.problem.nullSpecViolation=warning
org.eclipse.jdt.core.compiler.problem.nullUncheckedConversion=warning
org.eclipse.jdt.core.compiler.problem.potentialNullReference=warning
org.eclipse.jdt.core.compiler.source=1.7
org.eclipse.jdt.core.formatter.lineSplit=140
org.eclipse.jdt.core.formatter.tabulation.char=space
org.eclipse.jdt.core.formatter.tabulation.size=4
]]>
</content>
</file>
<file>
<name>.settings/org.eclipse.jdt.ui.prefs</name>
<content>
<![CDATA[eclipse.preferences.version=1
formatter_settings_version=12
# Intellij IDEA import order
org.eclipse.jdt.ui.importorder=;com;org;java;javax;\#;
# License header
org.eclipse.jdt.ui.text.custom_code_templates=<?xml version\="1.0" encoding\="UTF-8" standalone\="no"?><templates><template autoinsert\="false" context\="gettercomment_context" deleted\="false" description\="Comment for getter method" enabled\="true" id\="org.eclipse.jdt.ui.text.codetemplates.gettercomment" name\="gettercomment">/**\n *\n */</template><template autoinsert\="false" context\="settercomment_context" deleted\="false" description\="Comment for setter method" enabled\="true" id\="org.eclipse.jdt.ui.text.codetemplates.settercomment" name\="settercomment">/**\n *\n */</template><template autoinsert\="true" context\="constructorcomment_context" deleted\="false" description\="Comment for created constructors" enabled\="true" id\="org.eclipse.jdt.ui.text.codetemplates.constructorcomment" name\="constructorcomment">/**\n * ${tags}\n */</template><template autoinsert\="true" context\="filecomment_context" deleted\="false" description\="Comment for created Java files" enabled\="true" id\="org.eclipse.jdt.ui.text.codetemplates.filecomment" name\="filecomment">/**\n *\n */</template><template autoinsert\="false" context\="typecomment_context" deleted\="false" description\="Comment for created types" enabled\="true" id\="org.eclipse.jdt.ui.text.codetemplates.typecomment" name\="typecomment">/**\n *\n */</template><template autoinsert\="true" context\="fieldcomment_context" deleted\="false" description\="Comment for fields" enabled\="true" id\="org.eclipse.jdt.ui.text.codetemplates.fieldcomment" name\="fieldcomment">/**\n *\n */</template><template autoinsert\="true" context\="methodcomment_context" deleted\="false" description\="Comment for non-overriding methods" enabled\="true" id\="org.eclipse.jdt.ui.text.codetemplates.methodcomment" name\="methodcomment">/**\n * ${tags}\n */</template><template autoinsert\="false" context\="overridecomment_context" deleted\="false" description\="Comment for overriding methods" enabled\="true" id\="org.eclipse.jdt.ui.text.codetemplates.overridecomment" name\="overridecomment">/*\n *\n */</template><template autoinsert\="true" context\="delegatecomment_context" deleted\="false" description\="Comment for delegate methods" enabled\="true" id\="org.eclipse.jdt.ui.text.codetemplates.delegatecomment" name\="delegatecomment">/**\n * ${tags}\n * ${see_to_target}\n */</template><template autoinsert\="false" context\="newtype_context" deleted\="false" description\="Newly created files" enabled\="true" id\="org.eclipse.jdt.ui.text.codetemplates.newtype" name\="newtype">${filecomment}\n/*\n * Licensed to Elasticsearch under one or more contributor\n * license agreements. See the NOTICE file distributed with\n * this work for additional information regarding copyright\n * ownership. Elasticsearch licenses this file to you under\n * the Apache License, Version 2.0 (the "License"); you may\n * not use this file except in compliance with the License.\n * You may obtain a copy of the License at\n *\n * http://www.apache.org/licenses/LICENSE-2.0\n *\n * Unless required by applicable law or agreed to in writing,\n * software distributed under the License is distributed on an\n * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY\n * KIND, either express or implied. See the License for the\n * specific language governing permissions and limitations\n * under the License.\n */\n\n${package_declaration}\n\n${typecomment}\n${type_declaration}</template><template autoinsert\="true" context\="classbody_context" deleted\="false" description\="Code in new class type bodies" enabled\="true" id\="org.eclipse.jdt.ui.text.codetemplates.classbody" name\="classbody">\n</template><template autoinsert\="true" context\="interfacebody_context" deleted\="false" description\="Code in new interface type bodies" enabled\="true" id\="org.eclipse.jdt.ui.text.codetemplates.interfacebody" name\="interfacebody">\n</template><template autoinsert\="true" context\="enumbody_context" deleted\="false" description\="Code in new enum type bodies" enabled\="true" id\="org.eclipse.jdt.ui.text.codetemplates.enumbody" name\="enumbo
]]>
</content>
</file>
</additionalConfig>
create parent pom project from its original location
2015-06-05 07:12:05 -04:00
</configuration>
</plugin>
Add properties files to configure startup and installation scripts Many scripts are used to start/stop and install/uninstall elasticsearch. These scripts share a lot of configuration properties like directory paths, max value for a setting, default user etc. Most of the values are identical but some of them are different depending of the platform (Debian-based or Redhat-based OS), depending of the way elasticsearch is started (shell script, systemd, sysv-init...) or the way it is installed (zip, rpm, deb...). Today the values are duplicated in multiple places, making it difficult to maintain the scripts or to update a value. This pull request make this more uniform: values used in scripts must be defined in a common packaging.properties file. Each value can be overridden in another specific packaging.properties file for Debian or Redhat. All startup and installation scripts are filtered with the common then the custom packaging.properties files before being packaged as a zip/tar.gz/rpm/dpkf archive.
2015-03-30 09:58:34 -04:00
create parent pom project from its original location
2015-06-05 07:12:05 -04:00
<!-- Quality plugins (was static plugins) -->
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-jxr-plugin</artifactId>
<version>2.5</version>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-pmd-plugin</artifactId>
[build] Update to Apache Maven PMD Plugin 3.5 http://maven.apache.org/plugins/maven-pmd-plugin/ You should specify the version in your project's plugin configuration: ```xml <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-pmd-plugin</artifactId> <version>3.5</version> </plugin> ``` Release Notes - Apache Maven PMD Plugin - Version 3.5 --------------- Bug * [MPMD-208] Warning about deprecated Rule name when using rulesets/maven.xml * [MPMD-205] Javascript violations won't fail the build Improvement * [MPMD-211] Upgrade plexus-resources from 1.0-alpha-7 to 1.1 * [MPMD-209] Upgrade to PMD 5.3.2 * [MPMD-206] Make the sourceDirectories configurable New Feature * [MPMD-207] Support Javascript and JSP for CPD
2015-07-06 16:20:39 -04:00
<version>3.5</version>
create parent pom project from its original location
2015-06-05 07:12:05 -04:00
<configuration>
<rulesets>
<ruleset>${elasticsearch.tools.directory}/pmd/custom.xml</ruleset>
</rulesets>
<targetJdk>${maven.compiler.target}</targetJdk>
</configuration>
</plugin>
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>findbugs-maven-plugin</artifactId>
<version>3.0.0</version>
<configuration>
<xmlOutput>true</xmlOutput>
<xmlOutputDirectory>target/site</xmlOutputDirectory>
<fork>true</fork>
<maxHeap>2048</maxHeap>
<timeout>1800000</timeout>
<onlyAnalyze>org.elasticsearch.-</onlyAnalyze>
</configuration>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-project-info-reports-plugin</artifactId>
<version>2.7</version>
</plugin>
<plugin>
<groupId>org.jacoco</groupId>
<artifactId>jacoco-maven-plugin</artifactId>
<version>0.7.2.201409121644</version>
<executions>
<execution>
<id>default-prepare-agent</id>
<goals>
<goal>prepare-agent</goal>
</goals>
</execution>
<execution>
<id>default-report</id>
<phase>prepare-package</phase>
<goals>
<goal>report</goal>
</goals>
</execution>
<execution>
<id>default-check</id>
<goals>
<goal>check</goal>
</goals>
</execution>
</executions>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-antrun-plugin</artifactId>
<version>1.8</version>
<executions>
Packaging: Add LICENSE, NOTICE, and sha1 files and tests for all core dependencies Added a licenses/ directory to core which contains a sha1 file for each JAR dependency, and one or more LICENSE files and one NOTICE file for each project. Also adds dev-tools/src/main/resources/license-check/check_license_and_sha.pl which checks that the licenses/ dir is up to date during a mvn verify, and which can be used to update the sha1 files when upgrading dependencies. Closes #2794 Closes #10684 Closes #11705
2015-06-17 12:06:00 -04:00
<execution>
<id>check-license</id>
<phase>verify</phase>
<goals>
<goal>run</goal>
</goals>
<configuration>
<target>
<condition property="licenses.exists">
<available file="${basedir}/licenses" type="dir"/>
</condition>
<echo taskName="license check">Running license check</echo>
Get integration tests working on windows. We also run our license checker in `mvn verify`, but there are problems with checksum calculation on windows there, so I've disabled the license checker on windows to prevent those false fails.
2015-07-08 02:40:00 -04:00
<!-- on windows checksums are calculated wrong -->
<exec failonerror="${licenses.exists}" executable="perl" dir="${elasticsearch.tools.directory}/license-check" osfamily="unix" >
Packaging: Add LICENSE, NOTICE, and sha1 files and tests for all core dependencies Added a licenses/ directory to core which contains a sha1 file for each JAR dependency, and one or more LICENSE files and one NOTICE file for each project. Also adds dev-tools/src/main/resources/license-check/check_license_and_sha.pl which checks that the licenses/ dir is up to date during a mvn verify, and which can be used to update the sha1 files when upgrading dependencies. Closes #2794 Closes #10684 Closes #11705
2015-06-17 12:06:00 -04:00
<arg value="check_license_and_sha.pl"/>
<arg value="--check"/>
<arg value="${basedir}"/>
</exec>
</target>
</configuration>
</execution>
create parent pom project from its original location
2015-06-05 07:12:05 -04:00
<execution>
<id>set-permgen</id>
<phase>validate</phase>
<goals>
<goal>run</goal>
</goals>
<configuration>
<target>
<!-- if we are on java 1.7.* we set perm gen space since some tests need it otherwise we just inject a dummy value -->
<condition property="java.permGenSpace" value="-XX:MaxPermSize=128m" else="-Dsome.dummy.value=" >
<matches pattern="1\.7\..+$" string="${java.runtime.version}" />
</condition>
</target>
<exportAntProperties>true</exportAntProperties>
</configuration>
</execution>
<execution>
<id>check-invalid-patterns</id>
<phase>validate</phase>
<goals>
<goal>run</goal>
</goals>
<configuration>
<target unless="${validate.skip}">
<pathconvert pathsep="${line.separator}" dirsep="/" property="validate.patternsFound" setonempty="false">
<fileset dir="${basedir}">
<include name="**/*.java"/>
<include name="**/*.py"/>
<include name="**/*.txt"/>
<include name="**/*.xml"/>
<include name="**/*.rb"/>
<include name="**/*.pl"/>
<exclude name="**/org/elasticsearch/cluster/routing/shard_routes.txt"/>
<exclude name="**/target/**/*"/>
<exclude name="**/.metadata/**/*"/>
<exclude name="**/.idea/**/*"/>
<exclude name="**/eclipse-build/**/*"/>
<or>
<containsregexp expression="\t" casesensitive="no"/>
Add a release profile to the parent pom.xml This commit adds a release profile that runs additional checks like: * check for `norelease` in the source * check for `AwaitsFix` annotations * deploys only if all reactor builds where successful * signs all artifacts with the GPG key provided (required for release) * builds the RPM together with the zip, tar.gz and .deb during package phase Note this is WIP of replacing major functionality of the release pythong script but won't work by itself.
2015-07-14 06:04:16 -04:00
<containsregexp expression="${no.commit.pattern}" casesensitive="no"/>
create parent pom project from its original location
2015-06-05 07:12:05 -04:00
</or>
</fileset>
<map from="${basedir}${file.separator}" to="* "/>
</pathconvert>
<fail if="validate.patternsFound">The following files contain tabs or
nocommits:${line.separator}${validate.patternsFound}
</fail>
</target>
</configuration>
</execution>
<execution>
<phase>generate-test-resources</phase>
<id>create-heapdump-directory</id>
<configuration>
<target>
<echo taskname="heapdump" message="Creating heapdump directory"/>
<mkdir dir="${tests.heapdump.path}"/>
</target>
</configuration>
<goals>
<goal>run</goal>
</goals>
</execution>
<execution>
<id>tests-top-hints</id>
<phase>test</phase>
<configuration>
Add simple integ testing infra
2015-07-03 02:12:01 -04:00
<skip>${skip.unit.tests}</skip>
create parent pom project from its original location
2015-06-05 07:12:05 -04:00
<target>
Fix tophints noise. previously this was done wrong, junit4 ant tasks were brought into the test classpath. This created jar hell for tests, and also encouraged people to use _internal_ stuff like its bundled guava in tests. also the task was set to be lenient and ignore errors. And we were passing in a messload of unnecessary classpaths to run this. It only needs the module classpath: the explicit ant dependencies we declare.
2015-07-08 00:45:02 -04:00
<taskdef resource="com/carrotsearch/junit4/antlib.xml" classpathref="maven.plugin.classpath"/>
create parent pom project from its original location
2015-06-05 07:12:05 -04:00
<tophints max="${tests.topn}">
tophints is optional here, it might not exist
2015-07-16 22:46:41 -04:00
<fileset dir="${basedir}" includes="${execution.hint.file}"/>
create parent pom project from its original location
2015-06-05 07:12:05 -04:00
</tophints>
</target>
</configuration>
<goals>
<goal>run</goal>
</goals>
</execution>
</executions>
Fix tophints noise. previously this was done wrong, junit4 ant tasks were brought into the test classpath. This created jar hell for tests, and also encouraged people to use _internal_ stuff like its bundled guava in tests. also the task was set to be lenient and ignore errors. And we were passing in a messload of unnecessary classpaths to run this. It only needs the module classpath: the explicit ant dependencies we declare.
2015-07-08 00:45:02 -04:00
<dependencies>
<dependency>
<groupId>com.carrotsearch.randomizedtesting</groupId>
<artifactId>junit4-ant</artifactId>
<version>${testframework.version}</version>
</dependency>
</dependencies>
create parent pom project from its original location
2015-06-05 07:12:05 -04:00
</plugin>
<plugin>
<!-- We just declare which plugin version to use. Each project can have then its own settings -->
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-invoker-plugin</artifactId>
[build] Update maven-invoker-plugin to 2.0.0 Release Notes - Apache Maven Invoker Plugin - Version 2.0.0 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317525&version=12332831 Important Note: This Release is intended for the bug fix MINVOKER-187 and in this relationship is was necessary to upgrade the JDK minimum to JDK 1.6. This was the reason for the version upgrade to 2.0.0. Bug: * [MINVOKER-187] - Cloned IT project must be writable Improvement: * [MINVOKER-192] - Using fluido skin
2015-07-02 04:49:31 -04:00
<version>2.0.0</version>
create parent pom project from its original location
2015-06-05 07:12:05 -04:00
</plugin>
<plugin>
<!-- We just declare which plugin version to use. Each project can have then its own settings -->
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-javadoc-plugin</artifactId>
<version>2.10.3</version>
</plugin>
<plugin>
<!-- We just declare which plugin version to use. Each project can have then its own settings -->
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-verifier-plugin</artifactId>
<version>1.1</version>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-checkstyle-plugin</artifactId>
<version>2.15</version>
</plugin>
Calculate artifact checksums in maven Today we calculate the checksums in a python scritp to do the release. We can also do this way simpler in maven using an ant task.
2015-07-07 10:53:24 -04:00
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-install-plugin</artifactId>
<version>2.5.2</version>
<configuration>
<createChecksum>true</createChecksum>
</configuration>
</plugin>
create parent pom project from its original location
2015-06-05 07:12:05 -04:00
</plugins>
</pluginManagement>
Deploy artifacts to S3 as well as sonatype when running a release This change allows when running a release build with: ``` mvn -Prelease deploy ``` To deploy all artifacts to S3 as well as to sonatype at the same time. Both sources will be consistent in terms of content and no further action is required to publish our artifacts including .rpm, .deb, .zip, .tar.gz, .jar etc. on to out S3 download service. Albeit this changes the structure of our downloads to pretty much matching the maven repository layout, this makes releaseing core as well as the plugins extremely simple. This will allow to remove most of our python script used for release and it will automatically allow to release and integrate new modules without further interaction. This also allows us to bascially streamline our release process on CI such that CI builds can simply run maven deploy which is all we do during a release. With this commit only the git related modifications like tagging, version bumping on our pom files and publishing RPM and .deb in their dedicated repository is left for the python script. With this change our artifact are available as follows: ``` http://download.elasticsearch.org/elasticsearch/release/org/elasticsearch/elasticsearch/2.0.0-beta1/elasticsearch-2.0.0-beta1.deb http://download.elasticsearch.org/elasticsearch/release/org/elasticsearch/elasticsearch/2.0.0-beta1/elasticsearch-2.0.0-beta1.zip http://download.elasticsearch.org/elasticsearch/release/org/elasticsearch/elasticsearch/2.0.0-beta1/elasticsearch-2.0.0-beta1.rpm ``` Plugins are deployed to URLs like this: ``` http://download.elasticsearch.org/elasticsearch/release/org/elasticsearch/plugin/elasticsearch-analysis-icu/2.0.0-beta1/elasticsearch-analysis-icu-2.0.0-beta1.zip ``` All artifacts like .jar as well as their checksums and gpg signatures are also available next to it.
2015-07-14 16:20:46 -04:00
<extensions>
<extension>
<groupId>org.springframework.build</groupId>
<artifactId>aws-maven</artifactId>
<version>5.0.0.RELEASE</version>
</extension>
</extensions>
initial pom
2011-12-05 18:05:44 -05:00
</build>
code coverage hookup
2014-02-07 19:18:31 -05:00
<profiles>
create parent pom project from its original location
2015-06-05 07:12:05 -04:00
<profile>
<id>default</id>
<activation>
<activeByDefault>true</activeByDefault>
</activation>
<build>
<plugins>
<plugin>
<groupId>com.mycila</groupId>
<artifactId>license-maven-plugin</artifactId>
</plugin>
</plugins>
</build>
</profile>
Add a release profile to the parent pom.xml This commit adds a release profile that runs additional checks like: * check for `norelease` in the source * check for `AwaitsFix` annotations * deploys only if all reactor builds where successful * signs all artifacts with the GPG key provided (required for release) * builds the RPM together with the zip, tar.gz and .deb during package phase Note this is WIP of replacing major functionality of the release pythong script but won't work by itself.
2015-07-14 06:04:16 -04:00
<profile>
<id>release</id>
<properties>
<package.rpm>true</package.rpm>
<no.commit.pattern>\bno(n|)(release|commit)\b</no.commit.pattern> <!-- check for no-commit / no-release -->
Deploy artifacts to S3 as well as sonatype when running a release This change allows when running a release build with: ``` mvn -Prelease deploy ``` To deploy all artifacts to S3 as well as to sonatype at the same time. Both sources will be consistent in terms of content and no further action is required to publish our artifacts including .rpm, .deb, .zip, .tar.gz, .jar etc. on to out S3 download service. Albeit this changes the structure of our downloads to pretty much matching the maven repository layout, this makes releaseing core as well as the plugins extremely simple. This will allow to remove most of our python script used for release and it will automatically allow to release and integrate new modules without further interaction. This also allows us to bascially streamline our release process on CI such that CI builds can simply run maven deploy which is all we do during a release. With this commit only the git related modifications like tagging, version bumping on our pom files and publishing RPM and .deb in their dedicated repository is left for the python script. With this change our artifact are available as follows: ``` http://download.elasticsearch.org/elasticsearch/release/org/elasticsearch/elasticsearch/2.0.0-beta1/elasticsearch-2.0.0-beta1.deb http://download.elasticsearch.org/elasticsearch/release/org/elasticsearch/elasticsearch/2.0.0-beta1/elasticsearch-2.0.0-beta1.zip http://download.elasticsearch.org/elasticsearch/release/org/elasticsearch/elasticsearch/2.0.0-beta1/elasticsearch-2.0.0-beta1.rpm ``` Plugins are deployed to URLs like this: ``` http://download.elasticsearch.org/elasticsearch/release/org/elasticsearch/plugin/elasticsearch-analysis-icu/2.0.0-beta1/elasticsearch-analysis-icu-2.0.0-beta1.zip ``` All artifacts like .jar as well as their checksums and gpg signatures are also available next to it.
2015-07-14 16:20:46 -04:00
<forbidden.test.signatures>org.apache.lucene.util.LuceneTestCase$AwaitsFix @ Please fix all bugs before release or mark them as ignored</forbidden.test.signatures>
Add a release profile to the parent pom.xml This commit adds a release profile that runs additional checks like: * check for `norelease` in the source * check for `AwaitsFix` annotations * deploys only if all reactor builds where successful * signs all artifacts with the GPG key provided (required for release) * builds the RPM together with the zip, tar.gz and .deb during package phase Note this is WIP of replacing major functionality of the release pythong script but won't work by itself.
2015-07-14 06:04:16 -04:00
</properties>
<build>
<!-- sign the artifacts with GPG -->
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-gpg-plugin</artifactId>
<version>1.6</version>
<executions>
<execution>
<id>sign-artifacts</id>
<phase>verify</phase>
<goals>
<goal>sign</goal>
</goals>
<configuration>
<keyname>${gpg.keyname}</keyname>
<passphrase>${gpg.passphrase}</passphrase>
<defaultKeyring>${gpg.keyring}</defaultKeyring>
</configuration>
</execution>
</executions>
</plugin>
</plugins>
</build>
Deploy artifacts to S3 as well as sonatype when running a release This change allows when running a release build with: ``` mvn -Prelease deploy ``` To deploy all artifacts to S3 as well as to sonatype at the same time. Both sources will be consistent in terms of content and no further action is required to publish our artifacts including .rpm, .deb, .zip, .tar.gz, .jar etc. on to out S3 download service. Albeit this changes the structure of our downloads to pretty much matching the maven repository layout, this makes releaseing core as well as the plugins extremely simple. This will allow to remove most of our python script used for release and it will automatically allow to release and integrate new modules without further interaction. This also allows us to bascially streamline our release process on CI such that CI builds can simply run maven deploy which is all we do during a release. With this commit only the git related modifications like tagging, version bumping on our pom files and publishing RPM and .deb in their dedicated repository is left for the python script. With this change our artifact are available as follows: ``` http://download.elasticsearch.org/elasticsearch/release/org/elasticsearch/elasticsearch/2.0.0-beta1/elasticsearch-2.0.0-beta1.deb http://download.elasticsearch.org/elasticsearch/release/org/elasticsearch/elasticsearch/2.0.0-beta1/elasticsearch-2.0.0-beta1.zip http://download.elasticsearch.org/elasticsearch/release/org/elasticsearch/elasticsearch/2.0.0-beta1/elasticsearch-2.0.0-beta1.rpm ``` Plugins are deployed to URLs like this: ``` http://download.elasticsearch.org/elasticsearch/release/org/elasticsearch/plugin/elasticsearch-analysis-icu/2.0.0-beta1/elasticsearch-analysis-icu-2.0.0-beta1.zip ``` All artifacts like .jar as well as their checksums and gpg signatures are also available next to it.
2015-07-14 16:20:46 -04:00
<distributionManagement>
<repository>
<id>aws-release</id>
<name>AWS Release Repository</name>
<url>s3://download.elasticsearch.org/elasticsearch/release</url>
</repository>
<snapshotRepository>
<id>aws-snapshot</id>
<name>AWS Snapshot Repository</name>
<url>s3://download.elasticsearch.org/elasticsearch/snapshot</url>
</snapshotRepository>
</distributionManagement>
Add a release profile to the parent pom.xml This commit adds a release profile that runs additional checks like: * check for `norelease` in the source * check for `AwaitsFix` annotations * deploys only if all reactor builds where successful * signs all artifacts with the GPG key provided (required for release) * builds the RPM together with the zip, tar.gz and .deb during package phase Note this is WIP of replacing major functionality of the release pythong script but won't work by itself.
2015-07-14 06:04:16 -04:00
</profile>
Code style improvement
2014-08-29 03:01:05 -04:00
<!-- license profile, to generate third party license file -->
<profile>
<id>license</id>
<activation>
<property>
<name>license.generation</name>
<value>true</value>
</property>
</activation>
<!-- not including license-maven-plugin is sufficent to expose default license -->
</profile>
create parent pom project from its original location
2015-06-05 07:12:05 -04:00
<!-- omits noise -->
<profile>
<id>pom</id>
<activation>
<activeByDefault>false</activeByDefault>
<file>
<missing>${basedir}/src</missing>
</file>
</activation>
don't try to run tests for packaging=pom
2015-07-06 15:49:57 -04:00
<properties>
<skip.unit.tests>true</skip.unit.tests>
<skip.integ.tests>true</skip.integ.tests>
</properties>
create parent pom project from its original location
2015-06-05 07:12:05 -04:00
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-antrun-plugin</artifactId>
<executions>
<execution>
<id>create-heapdump-directory</id>
<phase>none</phase>
</execution>
<execution>
<id>tests-top-hints</id>
<phase>none</phase>
</execution>
</executions>
</plugin>
</plugins>
</build>
</profile>
<!-- skips validation checks -->
<profile>
<id>dev</id>
<build>
<plugins>
<plugin>
<groupId>de.thetaphi</groupId>
<artifactId>forbiddenapis</artifactId>
<executions>
<execution>
<id>check-forbidden-apis</id>
<phase>none</phase>
</execution>
<execution>
<id>check-forbidden-test-apis</id>
<phase>none</phase>
</execution>
</executions>
</plugin>
<plugin>
<groupId>com.mycila</groupId>
<artifactId>license-maven-plugin</artifactId>
<executions>
<execution>
<id>check-license-headers</id>
<phase>none</phase>
</execution>
</executions>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-antrun-plugin</artifactId>
<executions>
<execution>
<id>check-invalid-patterns</id>
<phase>none</phase>
</execution>
</executions>
</plugin>
</plugins>
</build>
</profile>
<!-- code coverage build -->
<profile>
<id>coverage</id>
<activation>
<property>
<name>tests.coverage</name>
<value>true</value>
</property>
</activation>
<dependencies>
<dependency>
<!-- must be on the classpath -->
<groupId>org.jacoco</groupId>
<artifactId>org.jacoco.agent</artifactId>
<classifier>runtime</classifier>
<scope>test</scope>
</dependency>
</dependencies>
<properties>
<tests.security.manager>false</tests.security.manager> <!-- security policy doesn't have appropriate permissions for instrumentation -->
</properties>
<build>
<plugins>
<plugin>
<groupId>org.jacoco</groupId>
<artifactId>jacoco-maven-plugin</artifactId>
</plugin>
</plugins>
</build>
</profile>
<!-- static analysis -->
<profile>
<id>static</id>
<activation>
<property>
<name>tests.static</name>
<value>true</value>
</property>
</activation>
<properties>
<tests.security.manager>false</tests.security.manager> <!-- security policy doesn't have appropriate permissions for instrumentation -->
</properties>
<build>
<plugins>
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>findbugs-maven-plugin</artifactId>
</plugin>
</plugins>
</build>
<reporting>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-jxr-plugin</artifactId>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-pmd-plugin</artifactId>
</plugin>
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>findbugs-maven-plugin</artifactId>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-project-info-reports-plugin</artifactId>
<version>2.7</version>
<reportSets>
<reportSet>
<reports>
<report>index</report>
</reports>
</reportSet>
</reportSets>
</plugin>
</plugins>
</reporting>
</profile>
code coverage hookup
2014-02-07 19:18:31 -05:00
</profiles>
create parent pom project from its original location
2015-06-05 07:12:05 -04:00
<modules>
<module>dev-tools</module>
Build: Make rest-spec-api a project so eclipse build works The change makes rest-spec-api a project in the same way as we build dev-tools. it packages the tests and api in a bundle using the maven-remote-resources-plugin and uses the same plugin in the plugins and core pom to unpack the rest-api-spec into the target directory and references the rest tests there in the test resources. The main stimulus for this change is that for those using Eclipse the current build does not work. After running `mvn eclipse:eclipse` the Eclipse IDE errors because the rest-api-spec is outside of the project scope, meaning that every time the command is run (required whenever any dependencies change), the class path of all the projects has to be manually fixed.
2015-06-18 10:05:42 -04:00
<module>rest-api-spec</module>
create parent pom project from its original location
2015-06-05 07:12:05 -04:00
<module>plugins</module>
add core module
2015-06-05 07:12:05 -04:00
<module>core</module>
create parent pom project from its original location
2015-06-05 07:12:05 -04:00
</modules>
Upgrade to Lucene 4.1 * Removed CustmoMemoryIndex in favor of MemoryIndex which as of 4.1 supports adding the same field twice * Replaced duplicated logic in X[*]FSDirectory for rate limiting with a RateLimitedFSDirectory wrapper * Remove hacks to find out merge context in rate limiting in favor of IOContext * replaced Scorer#freq() return type (from float to int) * Upgraded FVHighlighter to new 'centered' highlighting * Fixed RobinEngine to use seperate setCommitData
2013-01-22 06:21:37 -05:00
</project>