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

38 lines
1.2 KiB
Properties
Raw Normal View History

Introduce build qualifier parameter (#35155) * Introduce property to set version qualifier - VersionProperties.elasticsearch is now a string which can have qualifier and snapshot too - The Version class in the build no longer cares about snapshot and qualifier.
2018-11-01 23:27:40 -04:00
elasticsearch = 7.0.0
Update to lucene-8.0.0-snapshot-c78429a554 (#36212) Includes: * A fix for a bug in Intervals.or() (https://issues.apache.org/jira/browse/LUCENE-8586) * The ability to disable offset mangling in WordDelimiterGraphFilter (https://issues.apache.org/jira/browse/LUCENE-8509) * BM25Similarity no longer multiplies scores by k1 + 1
2018-12-05 07:43:56 -05:00
lucene = 8.0.0-snapshot-c78429a554
Build: Consolidate dependencies specified in multiple places Some dependencies must be specified in a couple places in the build. e.g. randomized runner is specified both in buildSrc (for the gradle wrapper plugin), as well as in the test-framework. This change creates buildSrc/versions.properties which acts similar to the set of shared version properties we used to have in the maven parent pom.
2015-11-10 02:34:22 -05:00
# optional dependencies
Upgrade to lucene-7.3.0-snapshot-98a6b3d. (#29298) Most notable changes include: - this release doesn't have the 7.2.1 version constant so I had to create one - spatial4j and jts were upgraded
2018-04-03 03:27:14 -04:00
spatial4j = 0.7
jts = 1.15.0
CORE: Upgrade to Jackson 2.8.11 (#32670) * closes #30352
2018-08-08 06:04:25 -04:00
jackson = 2.8.11
Upgrade to Jackson 2.8.10 (#27230) While it's not possible to upgrade the Jackson dependencies to their latest versions yet (see #27032 (comment) for more) it's still possible to upgrade to the latest 2.8.x version.
2017-11-06 04:20:05 -05:00
snakeyaml = 1.17
Move icu4j and super-csv version numbers to versions file (#32769) The upcoming ML log structure finder functionality will use these libraries, and it makes sense to use the same versions that are being used elsewhere in Elasticsearch. This is especially true with icu4j, which is pretty big.
2018-08-10 07:19:06 -04:00
icu4j = 62.1
supercsv = 2.4.0
Skip some logging tests on JDK 9 There is a bug in Log4j on JDK 9 for walking the stack to find where a log line is coming from. This bug is impacting some of our testing, so this commit marks these tests as skippable only on JDK 9 until the bug is fixed upstream. Relates #26467
2017-09-01 12:38:22 -04:00
# when updating log4j, please update also docs/java-api/index.asciidoc
LOGGING: Upgrade to Log4J 2.11.1 (#32616) * LOGGING: Upgrade to Log4J 2.11.1 * Upgrade to `2.11.1` to fix memory leaks in slow logger when logging large requests * This was caused by a bug in Log4J https://issues.apache.org/jira/browse/LOG4J2-2269 and is fixed in `2.11.1` via https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=9496c0c * Fixes #32537 * Fixes #27300
2018-08-06 08:56:21 -04:00
log4j = 2.11.1
Build: Consolidate dependencies specified in multiple places Some dependencies must be specified in a couple places in the build. e.g. randomized runner is specified both in buildSrc (for the gradle wrapper plugin), as well as in the test-framework. This change creates buildSrc/versions.properties which acts similar to the set of shared version properties we used to have in the maven parent pom.
2015-11-10 02:34:22 -05:00
slf4j = 1.6.2
Handle long paths on Windows for standalone tests In some cases our Windows builds fail due to long path names that arise from a combination of long build job names plus long sub-project names. While newer versions of Windows can handle long paths, invoking batch scripts longer than 260 characters via cmd.exe is still problematic. This leads to failing integration tests because we can not run the commands to install plugins, create the keystore, and start the node. This commit handles this by converting all paths on Windows used to start an Elasticsearch node to short path names. Relates #26365
2017-08-24 18:46:49 -04:00
# when updating the JNA version, also update the version in buildSrc/build.gradle
upgraded jna from 4.4.0-1 to 4.5.1 (#28183) Closes #28172
2018-01-11 11:31:10 -05:00
jna = 4.5.1
Build: Consolidate dependencies specified in multiple places Some dependencies must be specified in a couple places in the build. e.g. randomized runner is specified both in buildSrc (for the gradle wrapper plugin), as well as in the test-framework. This change creates buildSrc/versions.properties which acts similar to the set of shared version properties we used to have in the maven parent pom.
2015-11-10 02:34:22 -05:00
Upgrade Netty 4.3.32.Final (#36102) This commit upgrades netty. This will close #35360. Netty started throwing an IllegalArgumentException if a CompositeByteBuf is created with < 2 components. Netty4Utils was updated to reflect this change.
2018-11-30 11:02:10 -05:00
netty = 4.1.32.Final
Upgrade to Joda 2.10.1 (#35410) This version contains a bugfix that allows us to reenable one of our muted tests in DateTimeUnitTests. Closes #33749
2018-11-12 04:02:41 -05:00
joda = 2.10.1
NETWORKING: Upgrade Netty to 4.1.30 (#34417) * closes #34411
2018-10-12 11:13:28 -04:00
Build: Consolidate dependencies specified in multiple places Some dependencies must be specified in a couple places in the build. e.g. randomized runner is specified both in buildSrc (for the gradle wrapper plugin), as well as in the test-framework. This change creates buildSrc/versions.properties which acts similar to the set of shared version properties we used to have in the maven parent pom.
2015-11-10 02:34:22 -05:00
# test dependencies
Build: Fix reproduce info for methods with ( or ) (#35712) Our `REPRODUCE WITH` line wasn't working for tests with `(` or `)` in the method name. This isn't super common, but happens sometimes for our yml based rest tests. This is because randomized runner's globbing mechanism dind't escape `(` or `)`. I filed this upstream at https://github.com/randomizedtesting/randomizedtesting/issues/271 and Dawid kindly fixed the issue. This upgrades to pick up the fix. Closes #35692
2018-11-29 08:38:09 -05:00
randomizedrunner = 2.7.1
Upgrade to JUnit 4.12 (#23877) * Upgrade to JUnit 4.12 * Add permission to junit 4.12 and remove junit4-ant specific permission
2017-05-02 03:58:21 -04:00
junit = 4.12
update http client version to 4.5.2 and http-core 4.4.4 (#18399) StrictHostnameVerifier can now be removed
2016-05-20 06:02:42 -04:00
httpclient = 4.5.2
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
# When updating httpcore, please also update server/src/main/resources/org/elasticsearch/bootstrap/test-framework.policy
Build: upgrade httpcore version to 4.4.5 Closes #19127
2016-07-01 06:19:37 -04:00
httpcore = 4.4.5
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
# When updating httpasyncclient, please also update server/src/main/resources/org/elasticsearch/bootstrap/test-framework.policy
Remove connect SocketPermissions from core (#22797) This is related to #22116. Core no longer needs `SocketPermission` `connect`. This permission is relegated to these modules/plugins: - transport-netty4 module - reindex module - repository-url module - discovery-azure-classic plugin - discovery-ec2 plugin - discovery-gce plugin - repository-azure plugin - repository-gcs plugin - repository-hdfs plugin - repository-s3 plugin And for tests: - mocksocket jar - rest client - httpcore-nio jar - httpasyncclient jar
2017-02-03 10:39:56 -05:00
httpasyncclient = 4.1.2
Build: Remove transitive dependencies Transitive dependencies can be confusing and hard to deal with when conflicts arise between them. This change removes transitive dependencies from elasticsearch, and forces any dependency conflicts to be resolved manually, instead of automatically by gradle. closes #14627
2015-11-10 17:58:46 -05:00
commonslogging = 1.1.3
commonscodec = 1.10
Build: add hamcrest and securemock to version.properties
2016-06-06 09:02:52 -04:00
hamcrest = 1.3
Merge branch 'master' into feature/http_client
2016-06-17 07:50:18 -04:00
securemock = 1.2
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
# When updating mocksocket, please also update server/src/main/resources/org/elasticsearch/bootstrap/test-framework.policy
Introduce NioTransport into framework for testing (#24262) This commit introduces a nio based tcp transport into framework for testing. Currently Elasticsearch uses a simple blocking tcp transport for testing purposes (MockTcpTransport). This diverges from production where our current transport (netty) is non-blocking. The point of this commit is to introduce a testing variant that more closely matches the behavior of production instances.
2017-06-28 11:51:20 -04:00
mocksocket = 1.2
Remove connect SocketPermissions from core (#22797) This is related to #22116. Core no longer needs `SocketPermission` `connect`. This permission is relegated to these modules/plugins: - transport-netty4 module - reindex module - repository-url module - discovery-azure-classic plugin - discovery-ec2 plugin - discovery-gce plugin - repository-azure plugin - repository-gcs plugin - repository-hdfs plugin - repository-s3 plugin And for tests: - mocksocket jar - rest client - httpcore-nio jar - httpasyncclient jar
2017-02-03 10:39:56 -05:00
Add microbenchmarking infrastructure (#18891) With this commit we add a benchmarks project that contains the necessary build infrastructure and an example benchmark. It is added as a separate project to avoid interfering with the regular build too much (especially sanity checks) and to keep the microbenchmarks isolated. Microbenchmarks are generated with `gradle :benchmarks:jmhJar` and can be run with ` gradle :benchmarks:jmh`. We intentionally do not use the [jmh-gradle-plugin](https://github.com/melix/jmh-gradle-plugin) as it causes all sorts of problems (dependencies are not properly excluded, not all JMH parameters can be set) and it adds another abstraction layer that is not needed. Closes #18242
2016-06-15 10:48:02 -04:00
# benchmark dependencies
Upgrade to JMH 1.19
2017-12-29 04:56:47 -05:00
jmh = 1.19