honeymoose
/
OpenSearch
mirror of https://github.com/honeymoose/OpenSearch.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
OpenSearch/client/test/build.gradle

64 lines
2.3 KiB
Groovy
Raw Normal View History

[TEST] Add client-test module and make client tests use randomized runner directly The lucene-test dependency caused issues with IDEs as they would always load the lucene 5 jar although they shouldn't have, which caused jarhell in es core tests. If we depend directly on randomized runner we don't have this problem. It is luckily still compatible with java 1.7. This requires though adding a thin module that includes the base test class which can be shared between client and client-sniffer.
2016-06-22 13:22:48 -04:00
/*
* Licensed to Elasticsearch under one or more contributor
* license agreements. See the NOTICE file distributed with
* this work for additional information regarding copyright
* ownership. Elasticsearch licenses this file to you under
* the Apache License, Version 2.0 (the "License"); you may
* not use this file except in compliance with the License.
* You may obtain a copy of the License at
*
* http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing,
* software distributed under the License is distributed on an
* "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
* KIND, either express or implied. See the License for the
* specific language governing permissions and limitations
* under the License.
*/
import org.elasticsearch.gradle.precommit.PrecommitTasks
Revert shading for the low level rest client (#26367) At current, we do not feel there is enough of a reason to shade the low level rest client. It caused problems with commons logging and IDE's during the brief time it was used. We did not know exactly how many users will need this, and decided that leaving shading out until we gather more information is best. Users can still shade the jar themselves. For information and feeback, see issue #26366. Closes #26328 This reverts commit 3a209220464061d0e80e268a4755216362995194. This reverts commit 2c271f0f222b47ecba4aa68c887eb5f5e36f5050. This reverts commit 9d10dbea39951a48a2d7bd72160e1c00bde8512f. This reverts commit e816ef89a29337d88bb19d89e322d451efb3b6fb.
2017-08-25 15:13:12 -04:00
import org.gradle.api.JavaVersion
[TEST] Add client-test module and make client tests use randomized runner directly The lucene-test dependency caused issues with IDEs as they would always load the lucene 5 jar although they shouldn't have, which caused jarhell in es core tests. If we depend directly on randomized runner we don't have this problem. It is luckily still compatible with java 1.7. This requires though adding a thin module that includes the base test class which can be shared between client and client-sniffer.
2016-06-22 13:22:48 -04:00
apply plugin: 'elasticsearch.build'
apply plugin: 'ru.vyarus.animalsniffer'
targetCompatibility = JavaVersion.VERSION_1_7
sourceCompatibility = JavaVersion.VERSION_1_7
dependencies {
Revert shading for the low level rest client (#26367) At current, we do not feel there is enough of a reason to shade the low level rest client. It caused problems with commons logging and IDE's during the brief time it was used. We did not know exactly how many users will need this, and decided that leaving shading out until we gather more information is best. Users can still shade the jar themselves. For information and feeback, see issue #26366. Closes #26328 This reverts commit 3a209220464061d0e80e268a4755216362995194. This reverts commit 2c271f0f222b47ecba4aa68c887eb5f5e36f5050. This reverts commit 9d10dbea39951a48a2d7bd72160e1c00bde8512f. This reverts commit e816ef89a29337d88bb19d89e322d451efb3b6fb.
2017-08-25 15:13:12 -04:00
compile "org.apache.httpcomponents:httpcore:${versions.httpcore}"
[TEST] Add client-test module and make client tests use randomized runner directly The lucene-test dependency caused issues with IDEs as they would always load the lucene 5 jar although they shouldn't have, which caused jarhell in es core tests. If we depend directly on randomized runner we don't have this problem. It is luckily still compatible with java 1.7. This requires though adding a thin module that includes the base test class which can be shared between client and client-sniffer.
2016-06-22 13:22:48 -04:00
compile "com.carrotsearch.randomizedtesting:randomizedtesting-runner:${versions.randomizedrunner}"
compile "junit:junit:${versions.junit}"
compile "org.hamcrest:hamcrest-all:${versions.hamcrest}"
compile "org.codehaus.mojo:animal-sniffer-annotations:1.15"
signature "org.codehaus.mojo.signature:java17:1.0@signature"
}
forbiddenApisMain {
//client does not depend on core, so only jdk signatures should be checked
signaturesURLs = [PrecommitTasks.getResource('/forbidden/jdk-signatures.txt')]
}
forbiddenApisTest {
//we are using jdk-internal instead of jdk-non-portable to allow for com.sun.net.httpserver.* usage
bundledSignatures -= 'jdk-non-portable'
bundledSignatures += 'jdk-internal'
//client does not depend on core, so only jdk signatures should be checked
signaturesURLs = [PrecommitTasks.getResource('/forbidden/jdk-signatures.txt')]
}
Rename core module to server (#28180) This is related to #27933. It renames the core module to server. This is the first step towards introducing an elasticsearch-core jar.
2018-01-11 13:30:43 -05:00
// JarHell is part of es server, which we don't want to pull in
Introduce elasticsearch-core jar (#28191) This is related to #27933. It introduces a jar named elasticsearch-core in the lib directory. This commit moves the JarHell class from server to elasticsearch-core. Additionally, PathUtils and some of Loggers are moved as JarHell depends on them.
2018-01-15 11:59:01 -05:00
// TODO: Not anymore. Now in elasticsearch-core
[TEST] Add client-test module and make client tests use randomized runner directly The lucene-test dependency caused issues with IDEs as they would always load the lucene 5 jar although they shouldn't have, which caused jarhell in es core tests. If we depend directly on randomized runner we don't have this problem. It is luckily still compatible with java 1.7. This requires though adding a thin module that includes the base test class which can be shared between client and client-sniffer.
2016-06-22 13:22:48 -04:00
jarHell.enabled=false
// TODO: should we have licenses for our test deps?
dependencyLicenses.enabled = false
Build: Add 3rd party dependencies report generation (#27727) * Adds task dependenciesInfo to BuildPlugin to generate a CSV file with dependencies information (name,version,url,license) * Adds `ConcatFilesTask.groovy` to concatenates multiple files into one * Adds task `:distribution:generateDependenciesReport` to concatenate `dependencies.csv` files into a single file (`es-dependencies.csv` by default) # Examples: $ gradle dependenciesInfo :distribution:generateDependenciesReport ## Use `csv` system property to customize the output file path $ gradle dependenciesInfo :distribution:generateDependenciesReport -Dcsv=/tmp/elasticsearch-dependencies.csv ## When branch is not master, use `build.branch` system property to generate correct licenses URLs $ gradle dependenciesInfo :distribution:generateDependenciesReport -Dbuild.branch=6.x -Dcsv=/tmp/elasticsearch-dependencies.csv
2017-12-26 04:51:47 -05:00
dependenciesInfo.enabled = false
[TEST] Add client-test module and make client tests use randomized runner directly The lucene-test dependency caused issues with IDEs as they would always load the lucene 5 jar although they shouldn't have, which caused jarhell in es core tests. If we depend directly on randomized runner we don't have this problem. It is luckily still compatible with java 1.7. This requires though adding a thin module that includes the base test class which can be shared between client and client-sniffer.
2016-06-22 13:22:48 -04:00
namingConventions.enabled = false
//we aren't releasing this jar
thirdPartyAudit.enabled = false
Build: Remove old maven deploy support (#20403) * Build: Remove old maven deploy support This change removes the old maven deploy that we have in parallel to maven-publish, and makes maven-publish fully work with publishing to maven local. Using `gradle publishToMavenLocal` should be used to publish to .m2. Note that there is an unfortunate hack that means for zip artifacts we must first create/publish a dummy pom file, and then follow that with the real pom file. It would be nice to have the pom file contains packaging=zip, but maven central then requires sources and javadocs. But our zips are really just attached artifacts, so we already set the packaging type to pom for our zip files. This change just works around a limitation of the underlying maven publishing library which silently skips attached artifacts when the packaging type is set to pom. relates #20164 closes #20375 * Remove unnecessary extra spacing
2016-09-19 18:10:41 -04:00
test.enabled = false