My use case is to: start up an embedded ES for integration tests, configure it with checked in settings and mappings and index a test set of documents. This way I can fully test the various queries my system generates against known data, which is really helpful since regressions here aren't acceptable to my users.
I know I could treat ES like an external DB and run tests against that, but it'd be unfortunate to have to introduce all the environment-related issues which come along with this approach.
Is it possible to start publishing plugin artifacts to a maven repository again?
I've figured out how to do this in gradle. It's not pretty but it gives me a compile dependency on analysis-phonetic. I think this'll break down if I pull in, transitively or otherwise, dependencies which are provided by the plugin zip.
So it works, but it's a hack. Is there no chance of just going back to publishing these artifacts? I can't be the only one who needs a compile time dependency on plugins.
You're certainly not the only one. I reported the same thing in the past. It seems like the artifacts were taken down because Elastic think nobody should need them, without actually considering whether some of us were using them.
Even if Elastic want to maintain their own repository to host the files, you'd think they could at least make the structure the same as a real Maven repository so that we can continue to use normal methods of the build tool to download dependencies.