Do not apply StandaloneRestTestPlugin in StandaloneTestPlugin#86400
Do not apply StandaloneRestTestPlugin in StandaloneTestPlugin#86400breskeby merged 1 commit intoelastic:masterfrom
Conversation
As we are moving away from StandaloneRestTestPlugin (see elastic#85491) we want to reduce the surface of that plugin. If rest tests are used a rest test related plugin should be applied
|
Pinging @elastic/es-delivery (Team:Delivery) |
mark-vieira
left a comment
There was a problem hiding this comment.
We want to move away from this plugin as well, right? I mean, I'm pretty sure we could just swap this out for the elasticsearch.java plugin everywhere and it would just work. The only side-effect is we would be creating a main sourceset that doens't have any source in it and so those tasks would be noops. Do you intend to do this in a follow up PR?
|
Long term yes but at the moment, |
…c#86400) As we are moving away from StandaloneRestTestPlugin (see elastic#85491) we want to reduce the surface of that plugin. If rest tests are used a rest test related plugin should be applied
💚 Backport successful
|
…86400) (#86563) * Do not apply StandaloneRestTestPlugin in StandaloneTestPlugin (#86400) As we are moving away from StandaloneRestTestPlugin (see #85491) we want to reduce the surface of that plugin. If rest tests are used a rest test related plugin should be applied * Fix translog-policy build relying on standalone rest test plugin
As we are moving away from StandaloneRestTestPlugin (see #85491) we want to reduce the surface of that plugin.
If rest tests are used a rest test related plugin should be applied