Support for ES 7.16.3

[ptanov]

I wanted to contribute it and started fixing compilation errors (e.g. Builder is not a generic anymore, no BuilderContext but ContentPath in 7.11.2, etc.) but found that the last version of org.codelibs.elasticsearch.module/analysis-common is 7.10.2 as you mentioned here: elastic/elasticsearch#27527 (comment)
If you have time it will be perfect if you add support for ES 7.16.3.

Thanks

[jprante]

Sorry, but ES 7.10.2 is the last version I can support. AGPL 3.0 is not compatible to SSPL or Elastic 2.0 License.

[ptanov]

I see, thanks

[thaarbach]

@jprante Hi Jörg, i'm a little confused about

Sorry, but ES 7.10.2 is the last version I can support. AGPL 3.0 is not compatible to SSPL or Elastic 2.0 License.

I looked at Elastic's Licensing FAQ and it says that changing the licensing model doesn't affect the creation of plugins or their licensing:

I’m building plugins for Elasticsearch or Kibana, how does this change affect me?
This change does not affect how you build or license plugins to Elasticsearch or Kibana. For the avoidance of doubt, building a plugin to be used in Elasticsearch or Kibana does not constitute a derivative work, and will not have any impact on how you license the source code of your plugin.

If you have any questions, please reach out to us at [email protected]

Could explain, why it is not possible to support newer versions of elasticsearch?

[jprante]

@thaarbach It's simple. I use the AGPLv3 license, so everybody should be able to develop, modify, run, test, link, sell, distribute the plugin under AGPLv3. But that is no longer possible when the underlying Elasticsearch server that is required for developing, testing, and running is not AGPLv3 compatible. AGPLv3 makes strong assumptions about linked code at runtime. All linked components must be AGPLv3 compatible. So this is required for the Elasticsearch server. Until 7.10.2, the Apache License 2.0 worked, because it is AGPLv3 compatible. SSPL and Elastic 2.0 License are not compatible, they are unfriendly to GPLv3/AGPLv3 communities.

[thaarbach]

@jprante okay, but then is elastic lying about

and will not have any impact on how you license the source code of your plugin

It's really sad as it really is a great plugin that we've been using for years.

Thank you for your explanation and the great plugin.