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

47 lines
1.4 KiB
Properties
Raw Normal View History

Bump version to 7.6
2019-10-16 09:44:21 -04:00
elasticsearch = 7.6.0
Upgrade to lucene 8.4.0-snapshot-662c455. (#50016) (#50039) Lucene 8.4 is about to be released so we should check it doesn't cause problems with Elasticsearch.
2019-12-10 12:04:58 -05:00
lucene = 8.4.0-snapshot-662c455
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
Bundle AdoptOpenJDK 13 (#46860) This commit switches to use AdoptOpenJDK 13 for bundling the JDK, instead of Oracle OpenJDK 13.
2019-09-19 08:55:39 -04:00
bundled_jdk_vendor = adoptopenjdk
Bump bundled JDK to JDK 13.0.1+9 (#48587) This commit bumps the bundled JDK to 13.0.1+9. Since AdoptOpenJDK did not release 13.0.1+9 for Windows, this commit also enables that the bundled JDK version can vary by platform.
2019-10-28 12:30:43 -04:00
bundled_jdk = 13.0.1+9
Bundle java in distributions (#38013) * Bundle java in distributions Setting up a jdk is currently a required external step when installing elasticsearch. This is particularly problematic for the rpm/deb packages as installing a jdk in the same package installation command does not guarantee any order, so must be done in separate steps. Additionally, JAVA_HOME must be set and often causes problems in selecting a correct jdk when, for example, the system java is an older unsupported version. This commit bundles platform specific openjdks into each distribution. In addition to eliminating the issues above, it also presents future possible improvements like using jlink to build jdk images only containing modules that elasticsearch uses. closes #31845
2019-03-08 14:04:18 -05: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
# 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
Bump jackson-databind version for ingest-geoip (#39182) This commit bumps the jackson-databind version for ingest-geoip to 2.8.11.3.
2019-02-20 11:38:42 -05:00
# note that ingest-geoip has a hard-coded version; if you modify this version,
# you should also inspect that version to see if it can be advanced along with
# the com.maxmind.geoip2:geoip2 dependency
CORE: Upgrade to Jackson 2.8.11 (#32670) * closes #30352
2018-08-08 06:04:25 -04:00
jackson = 2.8.11
Update jackson-databind to 2.8.11.4 (#49347) (#49937)
2019-12-06 14:39:33 -05:00
jacksondatabind = 2.8.11.4
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 to Netty 4.1.43 (#48484) With this update we can remove the mitigation in our custom allocator which forces heap buffer allocations.
2019-10-25 11:36:07 -04:00
netty = 4.1.43.Final
Upgrade to joda 2.10.4 (#47805)
2019-10-31 09:26:35 -04:00
joda = 2.10.4
NETWORKING: Upgrade Netty to 4.1.30 (#34417) * closes #34411
2018-10-12 11:13:28 -04:00
Upgrade the bouncycastle dependency to 1.61 (#40017) This commit upgrades the bouncycastle dependency from 1.59 to 1.61.
2019-03-14 08:54:14 -04:00
# when updating this version, you need to ensure compatibility with:
# - plugins/ingest-attachment (transitive dependency, check the upstream POM)
# - distribution/tools/plugin-cli
# - x-pack/plugin/security
bouncycastle = 1.61
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-core and http-client dependencies (#46549) Relates to #45808 Closes #45577
2019-09-11 07:42:32 -04:00
httpclient = 4.5.10
httpcore = 4.4.12
Update httpclient for JDK 11 TLS engine (#37994) The apache commons http client implementations recently released versions that solve TLS compatibility issues with the new TLS engine that supports TLSv1.3 with JDK 11. This change updates our code to use these versions since JDK 11 is a supported JDK and we should allow the use of TLSv1.3.
2019-01-30 16:24:29 -05:00
httpasyncclient = 4.1.4
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
Update httpclient for JDK 11 TLS engine (#37994) The apache commons http client implementations recently released versions that solve TLS compatibility issues with the new TLS engine that supports TLSv1.3 with JDK 11. This change updates our code to use these versions since JDK 11 is a supported JDK and we should allow the use of TLSv1.3.
2019-01-30 16:24:29 -05:00
commonscodec = 1.11
Upgrade hamcrest to 2.1 (#41464) hamcrest has some improvements in newer versions, like FileMatchers that make assertions regarding file exists cleaner. This commit upgrades to the latest version of hamcrest so we can start using new and improved matchers.
2019-04-25 02:39:40 -04:00
hamcrest = 2.1
Merge branch 'master' into feature/http_client
2016-06-17 07:50:18 -04:00
securemock = 1.2
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