dubbo：3.0.8
dubbo-serialization-kryo：1.0.0
在序列化拓展包中没有排除dubbo-common模块导致项目启动报错
<dependency>
    <groupId>org.apache.dubbo.extensions</groupId>
    <artifactId>dubbo-serialization-kryo</artifactId>
    <exclusions>
        <!-- 这里存在一个引包bug,引入的是3.0.6的dubbo-coomon包导致项目启动不起来 而我当前使用的dubbo版本是3.0.8 -->
        <exclusion>
            <groupId>org.apache.dubbo</groupId>
            <artifactId>dubbo-common</artifactId>
        </exclusion>
    </exclusions>
</dependency>

经过上面的方式排除依赖后，项目才正常启动。

还有一个疑问，我采取dubbo协议时，optimizer指定的类被加载了，但是换成tri协议却不加载请问这是什么原因？
  # 协议名称
  name: tri
  # 序列化配置
  serialization: kryo
  # 序列化对象配置实现
  optimizer: com.grain.pay.service.api.serialization.SerializationOptimizerImpl
String VERSION_KEY = "version";
    String REVISION_KEY = "revision";
    String METADATA_KEY = "metadata-type";
    String REPORT_METADATA_KEY = "report-metadata";
    String REPORT_DEFINITION_KEY = "report-definition";
    String DEFAULT_METADATA_STORAGE_TYPE = "local";
    String REMOTE_METADATA_STORAGE_TYPE = "remote";
    String GENERIC_KEY = "generic";
    /**
     * The composite metadata storage type includes {@link #DEFAULT_METADATA_STORAGE_TYPE "local"} and
     * {@link #REMOTE_METADATA_STORAGE_TYPE "remote"}.
     *
     * @since 2.7.8
     */
    String COMPOSITE_METADATA_STORAGE_TYPE = "composite";
    /**
     * Consumer side 's proxy class
     */
    String PROXY_CLASS_REF = "refClass";
    /**
     * generic call
     */
    String $INVOKE = "$invoke";
    String $INVOKE_ASYNC = "$invokeAsync";
    String GENERIC_PARAMETER_DESC = "Ljava/lang/String;[Ljava/lang/String;[Ljava/lang/Object;";
    /**
     * echo call
     */
    String $ECHO = "$echo";
    /**