Fix module and package names for stable plugin api (#89772)
the convention for packages and module names is: org.elasticsearch.plugin[.analysis].api module-info.java and package-info.java were using incorrect names and not following the convention relates #88980
This commit is contained in:
parent
0302d2db2d
commit
2b6d4e97df
|
@ -6,7 +6,7 @@
|
|||
* Side Public License, v 1.
|
||||
*/
|
||||
|
||||
module org.elasticsearch.analysis.plugin.api {
|
||||
module org.elasticsearch.plugin.analysis.api {
|
||||
requires org.apache.lucene.core;
|
||||
requires org.elasticsearch.plugin.api;
|
||||
|
||||
|
|
|
@ -20,7 +20,7 @@ import java.lang.annotation.Target;
|
|||
@Target({ ElementType.TYPE })
|
||||
public @interface NamedComponent {
|
||||
/**
|
||||
* A name used for registration and lookup
|
||||
* The name used for registration and lookup
|
||||
* @return a name
|
||||
*/
|
||||
String name();
|
||||
|
|
|
@ -12,12 +12,12 @@
|
|||
* <ul>
|
||||
* <li> The root package is org.elasticsearch.plugin</li>
|
||||
* <li> Specialised API jars have their name following the root package.
|
||||
* i.e. org.elasticsearch.analysis
|
||||
* i.e. org.elasticsearch.plugin.analysis
|
||||
* </li>
|
||||
* <li> Interfaces and annotations used by plugin developers are in `api` package
|
||||
* i.e org.elasticsearch.analysis.api or org.elasticsearch.api
|
||||
* i.e org.elasticsearch.plugin.analysis.api or org.elasticsearch.plugin.api
|
||||
* <li> packages which are not meant to be used by plugin developers should not be subpackages of api
|
||||
* i.e org.elasticsearch.analysis.internal
|
||||
* i.e org.elasticsearch.plugin.analysis.internal
|
||||
* </li>
|
||||
* </ul>
|
||||
*/
|
||||
|
|
Loading…
Reference in New Issue