OpenSearch/x-pack/plugin/deprecation/build.gradle

evaluationDependsOn(xpackModule('core'))

apply plugin: 'elasticsearch.esplugin'
esplugin {
    name 'x-pack-deprecation'
    description 'Elasticsearch Expanded Pack Plugin - Deprecation'
    classname 'org.elasticsearch.xpack.deprecation.Deprecation'
    extendedPlugins = ['x-pack-core']
}
archivesBaseName = 'x-pack-deprecation'

dependencies {
    compileOnly "org.elasticsearch.plugin:x-pack-core:${version}"
}

run {
    plugin xpackModule('core')
}

integTest.enabled = false
Build: Replace references to x-pack-elasticsearch paths with helper methods (elastic/x-pack-elasticsearch#3748) In order to more easily integrate xpack once it moves into the elasticsearch repo, references to the existing x-pack-elasticsearch need to be reduced. This commit introduces a few helper "methods" available to any project within xpack (through gradle project extension properties, as closures). All refeerences to project paths now use these helper methods, except for those pertaining to bwc, which will be handled in a followup. Original commit: elastic/x-pack-elasticsearch@850668744c7188f3ca8d6ff561c99fbd8995288e 2018-01-27 00:48:30 -05:00			`evaluationDependsOn(xpackModule('core'))`
Force evaluation order between sub-plugins and core We are relying on the fact that :x-pack-elasticsearch:plugin:core is configured before these. This happens when these projects are alphabetically after core, but is not the case when they are not (ccr). To address this, we simplfy be explicit about evaluation order in all sub-plugins. Relates elastic/x-pack-elasticsearch#3663 Original commit: elastic/x-pack-elasticsearch@755f84258b8f2a8558de4437e76a3e9cc03d5b69 2018-01-22 10:55:03 -05:00
Split up xpack plugins into their own modules (elastic/x-pack-elasticsearch#3643) Thanks to some great work by a bunch of amazing people, the chuck norris xpack split is a go! Original commit: elastic/x-pack-elasticsearch@dad98e28f4043f805907af2ad441908f64ca6c70 2018-01-20 00:30:17 -05:00			`apply plugin: 'elasticsearch.esplugin'`
			`esplugin {`
			`name 'x-pack-deprecation'`
			`description 'Elasticsearch Expanded Pack Plugin - Deprecation'`
			`classname 'org.elasticsearch.xpack.deprecation.Deprecation'`
			`extendedPlugins = ['x-pack-core']`
			`}`
			`archivesBaseName = 'x-pack-deprecation'`

			`dependencies {`
Build: Rework shadow plugin configuration (#32409) This reworks how we configure the `shadow` plugin in the build. The major change is that we no longer bundle dependencies in the `compile` configuration, instead we bundle dependencies in the new `bundle` configuration. This feels more right because it is a little more "opt in" rather than "opt out" and the name of the `bundle` configuration is a little more obvious. As an neat side effect of this, the `runtimeElements` configuration used when one project depends on another now contains exactly the dependencies needed to run the project so you no longer need to reference projects that use the shadow plugin like this: ``` testCompile project(path: ':client:rest-high-level', configuration: 'shadow') ``` You can instead use the much more normal: ``` testCompile "org.elasticsearch.client:elasticsearch-rest-high-level-client:${version}" ``` 2018-08-21 20:03:28 -04:00			`compileOnly "org.elasticsearch.plugin:x-pack-core:${version}"`
Split up xpack plugins into their own modules (elastic/x-pack-elasticsearch#3643) Thanks to some great work by a bunch of amazing people, the chuck norris xpack split is a go! Original commit: elastic/x-pack-elasticsearch@dad98e28f4043f805907af2ad441908f64ca6c70 2018-01-20 00:30:17 -05:00			`}`

			`run {`
Build: Replace references to x-pack-elasticsearch paths with helper methods (elastic/x-pack-elasticsearch#3748) In order to more easily integrate xpack once it moves into the elasticsearch repo, references to the existing x-pack-elasticsearch need to be reduced. This commit introduces a few helper "methods" available to any project within xpack (through gradle project extension properties, as closures). All refeerences to project paths now use these helper methods, except for those pertaining to bwc, which will be handled in a followup. Original commit: elastic/x-pack-elasticsearch@850668744c7188f3ca8d6ff561c99fbd8995288e 2018-01-27 00:48:30 -05:00			`plugin xpackModule('core')`
Split up xpack plugins into their own modules (elastic/x-pack-elasticsearch#3643) Thanks to some great work by a bunch of amazing people, the chuck norris xpack split is a go! Original commit: elastic/x-pack-elasticsearch@dad98e28f4043f805907af2ad441908f64ca6c70 2018-01-20 00:30:17 -05:00			`}`
Test: Add internalClusterTest to xpack modules (elastic/x-pack-elasticsearch#3730) This commit reenables running ITs in xpack by adding an internalClusterTest to xpack modules that contain ESIntegTestCase tests. The new task allows us to run these independently of rest integ tests, which are disabled for xpack modules because installing the bundled plugins directly is not quite the same as installing via the meta plugin. Some tests (ML) are moved to their own qa module to accommodate the need for a real cluster. A couple tests (monitoring and upgrade) have been marked as AwaitsFix. Commits that have been folded into this commit: * Move ML IT tests to qa/ml-native-tests * Add internalClusterTest task and disable rest integ tests for xpack modules. Also tweak ML tests and get upgrade tests working * Adding the keystore and security back to the ml native tests * Fixing native integ test * Fix last ML test, add awaits fix to monitoring and upgrade tests * cleanup PR * fix checkstyle Original commit: elastic/x-pack-elasticsearch@3c0ed6fd3be2eaf57b561dce52c362c9d32c07a9 2018-01-25 04:38:34 -05:00
			`integTest.enabled = false`