As far as I understand, for plugin authors like me, and for the
Elasticsearch PluginManager in bin/plugin, this means a new situation,
since it restricts the possibility of downloading plugin zips from https://github.com/downloads/... to the existing files. For new ones, a new
location must be found.
Also, the Elasticsearch binary downloads are affected, but I'm confident a
solution for this will be found by elasticsearch.com team.
My suggestion for the plugin zip upload situation is
plugin zips should be placed into a 'downloads' subfolder in the plugin
root folder
the maven assembly plugin configuration should be modified to write the
zip into '${basedir}/downloads' for committing
and the PluginManager should be extended for looking
at https://raw.github.com///master/downloads/-.zip
The PluginManager should be compiled in its own jar so that existing
cluster can install plugins without upgrading. Of course, file-based
installs will still work.
As far as I understand, for plugin authors like me, and for the
Elasticsearch PluginManager in bin/plugin, this means a new situation,
since it restricts the possibility of downloading plugin zips from https://github.com/downloads/... to the existing files. For new ones, a
new location must be found.
Also, the Elasticsearch binary downloads are affected, but I'm confident a
solution for this will be found by elasticsearch.com team.
My suggestion for the plugin zip upload situation is
plugin zips should be placed into a 'downloads' subfolder in the plugin
root folder
the maven assembly plugin configuration should be modified to write the
zip into '${basedir}/downloads' for committing
and the PluginManager should be extended for looking at https://raw.github.com/
//master/downloads/-.zip
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.