Change Details

Today the process to deploy elasticsearch plugins is complex and requires a lot of manual steps. - Every jar present in a plugin zip file needs to be uploaded manually to archiva.wikimedia.org - a patch to operations/software/elasticsearch/plugins needs to be made - someone must verify that the md5 of every files can be retrieved from archiva.wikimedia.org - Some jar are no longer official maven dependencies and are not available outside the zip file itself (e.g. analysis-icu-5.2.1.jar in analysis-icu-5.2.1.zip) The steps to upload artifacts to archiva.wikimedia.org is a pain, all plugin dependencies need to be uploaded manually, e.g. fo analysis-icu: - upload com.ibm.icu:icu4j - upload org.apache.lucene:lucene-analysis-icu - upload a fake artifact (auto generate pom) for org.elasticsearch.plugin:analysis-icu (Every upload require filling 4 text boxes) This is not straightforward, error-prone and time-consuming. We should find a process that is more fluent/automatic. Possible solutions: - create a custom deb package to bundle all the required plugins, ideally working directly with zip distributions.

Today the process to deploy elasticsearch plugins is complex and requires a lot of manual steps. - Every jar present in a plugin zip file needs to be uploaded manually to archiva.wikimedia.org - a patch to operations/software/elasticsearch/plugins needs to be made - someone must verify that the md5 of every files can be retrieved from archiva.wikimedia.org - Some jar are no longer official maven dependencies and are not available outside the zip file itself (e.g. analysis-icu-5.2.1.jar in analysis-icu-5.2.1.zip) The steps to upload artifacts to archiva.wikimedia.org is a pain, all plugin dependencies need to be uploaded manually, e.g. for analysis-icu: - upload com.ibm.icu:icu4j - upload org.apache.lucene:lucene-analysis-icu - upload a fake artifact (auto generate pom) for org.elasticsearch.plugin:analysis-icu (Every upload require filling 4 text boxes) This is not straightforward, error-prone and time-consuming. We should find a process that is more fluent/automatic. Possible solutions: - create a custom deb package to bundle all the required plugins, ideally working directly with zip distributions.

Today the process to deploy elasticsearch plugins is complex and requires a lot of manual steps. - Every jar present in a plugin zip file needs to be uploaded manually to archiva.wikimedia.org - a patch to operations/software/elasticsearch/plugins needs to be made - someone must verify that the md5 of every files can be retrieved from archiva.wikimedia.org - Some jar are no longer official maven dependencies and are not available outside the zip file itself (e.g. analysis-icu-5.2.1.jar in analysis-icu-5.2.1.zip) The steps to upload artifacts to archiva.wikimedia.org is a pain, all plugin dependencies need to be uploaded manually, e.g. for analysis-icu: - upload com.ibm.icu:icu4j - upload org.apache.lucene:lucene-analysis-icu - upload a fake artifact (auto generate pom) for org.elasticsearch.plugin:analysis-icu (Every upload require filling 4 text boxes) This is not straightforward, error-prone and time-consuming. We should find a process that is more fluent/automatic. Possible solutions: - create a custom deb package to bundle all the required plugins, ideally working directly with zip distributions.