dependencies-private.txt是自己新建和填写的吗？ #2520

pilgrim773 · 2023-02-21T13:17:22Z

pilgrim773
Feb 21, 2023

jar包里的META-INF.mirai-console-plugin.dependencies-private.txt 和META-INF.mirai-console-plugin.dependencies-shared.txt是如何生成的，是gradle的task生成吗？如果是开发者自己需要创建请问是哪次更新的文档提到了这两个文件？
另外我的项目还用着Groovy DSL的gradle，无法使用mirai这个task，会报
Could not find method mirai() for arguments [build_bwxrf2iysvzc4mqngg6oxo947$_run_closure8@242b140b] on root project 'pihuabot' of type org.gradle.api.Project.

Answered by Karlatemp

Feb 21, 2023

这两个文件会在执行 buildPlugin 的时候生成，你不需要自己生成这两个文件

当然，如果你因为某些原因必须自己编写，这两个文件的格式是 $group:$ artifact:$version (如 org.example:mylib:1.0.0)

一行一条，支持空行，不支持注释

View full answer

cssxsh · 2023-02-21T13:45:21Z

cssxsh
Feb 21, 2023

汇报问题请附上版本信息

0 replies

Karlatemp · 2023-02-21T14:24:50Z

Karlatemp
Feb 21, 2023
Maintainer

这两个文件会在执行 buildPlugin 的时候生成，你不需要自己生成这两个文件

当然，如果你因为某些原因必须自己编写，这两个文件的格式是 $group:$ artifact:$version (如 org.example:mylib:1.0.0)

一行一条，支持空行，不支持注释

1 reply

pilgrim773 Feb 21, 2023
Author

我找错了打包出来的jar的生成路径，看了一下新项目确实有了。感谢

pilgrim773 · 2023-02-21T15:32:23Z

pilgrim773
Feb 21, 2023
Author

目前问题：使用dependencies-private.txt试图精简化插件jar包时（原来我使用shadowJar打包全依赖，插件大小达到了13M），出现了
和#2155一样的问题，第三方包Reflections无法扫描包名，使用Reflections reflections = new Reflections(packageName)目前会报java.lang.NoClassDefFoundError: com/google/common/collect/Multimap

暂时没有时间研究解决方案，先记在这里…

4 replies

cssxsh Feb 21, 2023

目前问题：使用dependencies-private.txt试图精简化插件jar包时（原来我使用shadowJar打包全依赖，插件大小达到了13M），出现了和这个一样的问题，第三方包Reflections无法扫描包名，使用Reflections reflections = new Reflections(packageName)目前会报java.lang.NoClassDefFoundError: com/google/common/collect/Multimap

暂时没有时间研究解决方案，先记在这里…

看样子你不是很懂 reflections 的原理

你需要给 reflections 指定一下类加载器
比如下面这个例子

https://github.com/cssxsh/mirai-hibernate-plugin/blob/59327bd4b3ed14299da96c7a825161d929050fe0/src/main/kotlin/xyz/cssxsh/mirai/hibernate/MiraiHibernateConfiguration.kt#L42-L45

pilgrim773 Feb 21, 2023
Author

确实没想过花时间去看工具包的原理，这个例子是kotlin的我也很难明白。其实反射和类加载这两个概念本身就不熟…… 我的疑惑是当把reflections包交给mcl下载进plugins-libraries目录时会扫描反射失效，但现在我是保留它让它随插件一起打入插件jar就报上面那个错

cssxsh Feb 21, 2023

确实没想过花时间去看工具包的原理，这个例子是kotlin的我也很难明白。其实反射和类加载这两个概念本身就不熟…… 我的疑惑是当把reflections包交给mcl下载进plugins-libraries目录时会扫描反射失效，但现在我是保留它让它随插件一起打入插件jar就报上面那个错

给你改成 java 了
罗里吧嗦

        var builder = new org.reflections.util.ConfigurationBuilder();
        builder.forPackage("包名", this.getClass().getClassLoader());
        var reflections = new org.reflections.Reflections(builder);

pilgrim773 Feb 21, 2023
Author

首先真的很谢谢能提供帮助，您第一次给我例子的时候我就看到了那个loader是一个自定义类加载器，而我的项目没有定义，所以我自己肯定也会花更多时间去研究我需要一个怎样的类加载器，而不是直接要答案。您何必又用这样的语气呢

pilgrim773 · 2023-02-21T18:31:56Z

pilgrim773
Feb 21, 2023
Author

找到一个去年的帖子，按照他的办法在主类onEnable方法使用
Reflections reflector=new Reflections("com.pihua.plugin",getLoader().getClassLoaders().toArray());的话，会报个org.reflections.ReflectionsException: could not use param 'JvmPluginClassLoader{mirai-api-http-2.8.0.mirai2.jar}'`

串到别的插件去了，本来以为多插件情况不适合用，就继续用

reflections = new Reflections("com.pihua.plugin", this.getClass().getClassLoader());

但是也报以下异常，这回是自己的插件名了

org.reflections.ReflectionsException: could not use param 'JvmPluginClassLoader{koyukiBot-2.2.6-dev.jar}'
2023-02-22 02:22:26 W/stderr:   at koyukiBot-2.2.6-dev.jar[private]//org.reflections.util.ConfigurationBuilder.build(ConfigurationBuilder.java:100)
2023-02-22 02:22:26 W/stderr:   at koyukiBot-2.2.6-dev.jar[private]//org.reflections.Reflections.<init>(Reflections.java:159)
2023-02-22 02:22:26 W/stderr:   at koyukiBot-2.2.6-dev.jar//com.pihua.plugin.AskAndAnswerPluginMain.onLoad(AskAndAnswerPluginMain.java:78)
2023-02-22 02:22:26 W/stderr:   at net.mamoe.mirai.console.internal.plugin.JvmPluginInternal.internalOnLoad$mirai_console(JvmPluginInternal.kt:248)
2023-02-22 02:22:26 W/stderr:   at net.mamoe.mirai.console.internal.plugin.BuiltInJvmPluginLoaderImpl.load(BuiltInJvmPluginLoaderImpl.kt:283)
2023-02-22 02:22:26 W/stderr:   at net.mamoe.mirai.console.internal.plugin.BuiltInJvmPluginLoaderImpl.load(BuiltInJvmPluginLoaderImpl.kt:35)
2023-02-22 02:22:26 W/stderr:   at net.mamoe.mirai.console.plugin.jvm.JvmPluginLoader$BuiltIn.load(JvmPluginLoader.kt)
2023-02-22 02:22:26 W/stderr:   at net.mamoe.mirai.console.plugin.jvm.JvmPluginLoader$BuiltIn.load(JvmPluginLoader.kt:50)
2023-02-22 02:22:26 W/stderr:   at net.mamoe.mirai.console.internal.plugin.PluginManagerImpl.loadPluginNoEnable(PluginManagerImpl.kt:90)
2023-02-22 02:22:26 W/stderr:   at net.mamoe.mirai.console.internal.plugin.PluginManagerImpl.loadAllPluginsUsingBuiltInLoaders$mirai_console(PluginManagerImp
l.kt:146)
2023-02-22 02:22:26 W/stderr:   at net.mamoe.mirai.console.internal.MiraiConsoleImplementationBridge.doStart$mirai_console(MiraiConsoleImplementationBridge.k
t:279)
2023-02-22 02:22:26 W/stderr:   at net.mamoe.mirai.console.MiraiConsoleImplementation$Companion.start(MiraiConsoleImplementation.kt:508)
2023-02-22 02:22:26 W/stderr:   at net.mamoe.mirai.console.terminal.MiraiConsoleTerminalLoader.startAsDaemon(MiraiConsoleTerminalLoader.kt:177)
2023-02-22 02:22:26 W/stderr:   at net.mamoe.mirai.console.terminal.MiraiConsoleTerminalLoader.startAsDaemon$default(MiraiConsoleTerminalLoader.kt:176)
2023-02-22 02:22:26 W/stderr:   at net.mamoe.mirai.console.terminal.MiraiConsoleTerminalLoader.main(MiraiConsoleTerminalLoader.kt:54)
2023-02-22 02:22:26 W/stderr:   at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
2023-02-22 02:22:26 W/stderr:   at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
2023-02-22 02:22:26 W/stderr:   at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
2023-02-22 02:22:26 W/stderr:   at java.base/java.lang.reflect.Method.invoke(Method.java:566)
2023-02-22 02:22:26 W/stderr:   at org.itxtech.mcl.Utility.bootJars(Utility.java:86)
2023-02-22 02:22:26 W/stderr:   at org.itxtech.mcl.Utility.bootJars(Utility.java:76)
2023-02-22 02:22:26 W/stderr:   at org.itxtech.mcl.Utility.bootMirai(Utility.java:98)
2023-02-22 02:22:26 W/stderr:   at org.itxtech.mcl.module.builtin.Boot.boot(Boot.java:113)
2023-02-22 02:22:26 W/stderr:   at org.itxtech.mcl.module.ModuleManager.phaseBoot(ModuleManager.java:123)
2023-02-22 02:22:26 W/stderr:   at org.itxtech.mcl.Loader.lambda$start$4(Loader.java:196)
2023-02-22 02:22:26 W/stderr:   at org.itxtech.mcl.Loader.tryCatching(Loader.java:151)
2023-02-22 02:22:26 W/stderr:   at org.itxtech.mcl.Loader.start(Loader.java:196)
2023-02-22 02:22:26 W/stderr:   at org.itxtech.mcl.Loader.main(Loader.java:84)

4 replies

cssxsh Feb 22, 2023

找到一个去年的帖子，按照他的办法在主类onEnable方法使用 Reflections reflector=new Reflections("com.pihua.plugin",getLoader().getClassLoaders().toArray());的话，会报个org.reflections.ReflectionsException: could not use param 'JvmPluginClassLoader{mirai-api-http-2.8.0.mirai2.jar}'`

串到别的插件去了，本来以为多插件情况不适合用，就继续用

reflections = new Reflections("com.pihua.plugin", this.getClass().getClassLoader());

但是也报以下异常，这回是自己的插件名了

org.reflections.ReflectionsException: could not use param 'JvmPluginClassLoader{koyukiBot-2.2.6-dev.jar}'
2023-02-22 02:22:26 W/stderr:   at koyukiBot-2.2.6-dev.jar[private]//org.reflections.util.ConfigurationBuilder.build(ConfigurationBuilder.java:100)
2023-02-22 02:22:26 W/stderr:   at koyukiBot-2.2.6-dev.jar[private]//org.reflections.Reflections.<init>(Reflections.java:159)
2023-02-22 02:22:26 W/stderr:   at koyukiBot-2.2.6-dev.jar//com.pihua.plugin.AskAndAnswerPluginMain.onLoad(AskAndAnswerPluginMain.java:78)
2023-02-22 02:22:26 W/stderr:   at net.mamoe.mirai.console.internal.plugin.JvmPluginInternal.internalOnLoad$mirai_console(JvmPluginInternal.kt:248)
2023-02-22 02:22:26 W/stderr:   at net.mamoe.mirai.console.internal.plugin.BuiltInJvmPluginLoaderImpl.load(BuiltInJvmPluginLoaderImpl.kt:283)
2023-02-22 02:22:26 W/stderr:   at net.mamoe.mirai.console.internal.plugin.BuiltInJvmPluginLoaderImpl.load(BuiltInJvmPluginLoaderImpl.kt:35)
2023-02-22 02:22:26 W/stderr:   at net.mamoe.mirai.console.plugin.jvm.JvmPluginLoader$BuiltIn.load(JvmPluginLoader.kt)
2023-02-22 02:22:26 W/stderr:   at net.mamoe.mirai.console.plugin.jvm.JvmPluginLoader$BuiltIn.load(JvmPluginLoader.kt:50)
2023-02-22 02:22:26 W/stderr:   at net.mamoe.mirai.console.internal.plugin.PluginManagerImpl.loadPluginNoEnable(PluginManagerImpl.kt:90)
2023-02-22 02:22:26 W/stderr:   at net.mamoe.mirai.console.internal.plugin.PluginManagerImpl.loadAllPluginsUsingBuiltInLoaders$mirai_console(PluginManagerImp
l.kt:146)
2023-02-22 02:22:26 W/stderr:   at net.mamoe.mirai.console.internal.MiraiConsoleImplementationBridge.doStart$mirai_console(MiraiConsoleImplementationBridge.k
t:279)
2023-02-22 02:22:26 W/stderr:   at net.mamoe.mirai.console.MiraiConsoleImplementation$Companion.start(MiraiConsoleImplementation.kt:508)
2023-02-22 02:22:26 W/stderr:   at net.mamoe.mirai.console.terminal.MiraiConsoleTerminalLoader.startAsDaemon(MiraiConsoleTerminalLoader.kt:177)
2023-02-22 02:22:26 W/stderr:   at net.mamoe.mirai.console.terminal.MiraiConsoleTerminalLoader.startAsDaemon$default(MiraiConsoleTerminalLoader.kt:176)
2023-02-22 02:22:26 W/stderr:   at net.mamoe.mirai.console.terminal.MiraiConsoleTerminalLoader.main(MiraiConsoleTerminalLoader.kt:54)
2023-02-22 02:22:26 W/stderr:   at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
2023-02-22 02:22:26 W/stderr:   at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
2023-02-22 02:22:26 W/stderr:   at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
2023-02-22 02:22:26 W/stderr:   at java.base/java.lang.reflect.Method.invoke(Method.java:566)
2023-02-22 02:22:26 W/stderr:   at org.itxtech.mcl.Utility.bootJars(Utility.java:86)
2023-02-22 02:22:26 W/stderr:   at org.itxtech.mcl.Utility.bootJars(Utility.java:76)
2023-02-22 02:22:26 W/stderr:   at org.itxtech.mcl.Utility.bootMirai(Utility.java:98)
2023-02-22 02:22:26 W/stderr:   at org.itxtech.mcl.module.builtin.Boot.boot(Boot.java:113)
2023-02-22 02:22:26 W/stderr:   at org.itxtech.mcl.module.ModuleManager.phaseBoot(ModuleManager.java:123)
2023-02-22 02:22:26 W/stderr:   at org.itxtech.mcl.Loader.lambda$start$4(Loader.java:196)
2023-02-22 02:22:26 W/stderr:   at org.itxtech.mcl.Loader.tryCatching(Loader.java:151)
2023-02-22 02:22:26 W/stderr:   at org.itxtech.mcl.Loader.start(Loader.java:196)
2023-02-22 02:22:26 W/stderr:   at org.itxtech.mcl.Loader.main(Loader.java:84)

你没看我给的例子吗，都让你用 ConfigurationBuilder.forPackage 了, 另外 var 就是 java 的语法，你不喜欢可以改

        ConfigurationBuilder builder = new ConfigurationBuilder();
        builder.forPackage("com.pihua.plugin", this.getClass().getClassLoader());
        Reflections reflections = new Reflections(builder);

pilgrim773 Feb 22, 2023
Author

这个写法也试了，写在onLoad方法或者onEnable里，抛出
java.lang.NoClassDefFoundError:org/reflections/Configuration
mcl的控制台输出没法往上翻，我只能看到最低层的错误是这个，上层的信息看不到。而且console启动失败所以也没输出进log文件。感觉依赖树出问题了，回去再试试

cssxsh Feb 22, 2023

这个写法也试了，写在onLoad方法或者onEnable里，抛出 java.lang.NoClassDefFoundError:org/reflections/Configuration mcl的控制台输出没法往上翻，我只能看到最低层的错误是这个，上层的信息看不到。而且console启动失败所以也没输出进log文件。感觉依赖树出问题了，回去再试试

mcl的控制台输出没法往上翻
日志文件在 logs 文件夹，
另外你可以使用 runConsole 在idea里启动控制台
那时就是 debug-sandbox/logs

java.lang.NoClassDefFoundError 说明依赖没加载上，你没有使用 buildPlugin 打包插件吗，打包结果在 build/mirai

pilgrim773 Feb 22, 2023
Author

对，我说的就是logs里的日志没有记录这个找不到类的异常。前面那个异常
could not use param 'JvmPluginClassLoader
是有控制台打印也有文件记录，mcl是启动成功的。而这个NoClassDefFoundError有控制台打印但没有写入log文件，并且mcl启动不起来。所以我猜测必须mcl成功运行起来了才会写文件？
我的项目是早期版本idea 2020建立的groovy dsl的gradle项目，不是mirai-console插件模板，所以没有插件版gradle所带的 mirai这个闭包，没有buildPlugin可用。
今晚我会尝试整个项目迁移进新模板里再看看。
不过我觉得不应该是这个反射包的加载问题，因为已经使用过Reflections类的构造器了(就是第一次抛的那个异常)，大概……不可能只加载了一半，另一半有问题吧。

pilgrim773 · 2023-02-22T11:32:40Z

pilgrim773
Feb 22, 2023
Author

确认到ClassNotFoundException异常，这次重构了项目使用插件新模板构建，runConsole来启动测试，控制台抛出：

net.mamoe.mirai.console.internal.util.ServiceLoadException: Could not load service com.pihua.plugin.AskAndAnswerPluginMain.
	at net.mamoe.mirai.console.internal.util.PluginServiceHelper.loadService(PluginServiceHelper.kt:60)
	at net.mamoe.mirai.console.internal.util.PluginServiceHelper.loadAllServices(PluginServiceHelper.kt:42)
	at net.mamoe.mirai.console.internal.plugin.BuiltInJvmPluginLoaderImpl$extractPlugins$findAllInstances$2.invoke(BuiltInJvmPluginLoaderImpl.kt:197)
	at net.mamoe.mirai.console.internal.plugin.BuiltInJvmPluginLoaderImpl$extractPlugins$findAllInstances$2.invoke(BuiltInJvmPluginLoaderImpl.kt:192)
	at kotlin.sequences.TransformingSequence$iterator$1.next(Sequences.kt:210)
	at kotlin.sequences.FlatteningSequence$iterator$1.ensureItemIterator(Sequences.kt:314)
	at kotlin.sequences.FlatteningSequence$iterator$1.hasNext(Sequences.kt:303)
	at kotlin.sequences.TransformingSequence$iterator$1.hasNext(Sequences.kt:214)
	at kotlin.sequences.TransformingSequence$iterator$1.hasNext(Sequences.kt:214)
	at kotlin.sequences.FlatteningSequence$iterator$1.ensureItemIterator(Sequences.kt:316)
	at kotlin.sequences.FlatteningSequence$iterator$1.hasNext(Sequences.kt:303)
	at kotlin.sequences.SequencesKt___SequencesKt.toCollection(_Sequences.kt:787)
	at kotlin.sequences.SequencesKt___SequencesKt.toSet(_Sequences.kt:828)
	at net.mamoe.mirai.console.internal.plugin.BuiltInJvmPluginLoaderImpl.extractPlugins(BuiltInJvmPluginLoaderImpl.kt:218)
	at net.mamoe.mirai.console.internal.plugin.BuiltInJvmPluginLoaderImpl.listPlugins(BuiltInJvmPluginLoaderImpl.kt:67)
	at net.mamoe.mirai.console.plugin.jvm.JvmPluginLoader$BuiltIn.listPlugins(JvmPluginLoader.kt)
	at net.mamoe.mirai.console.internal.plugin.PluginManagerImpl.listAndSortAllPlugins(PluginManagerImpl.kt:195)
	at net.mamoe.mirai.console.internal.plugin.PluginManagerImpl.findAndSortAllPluginsUsingBuiltInLoaders(PluginManagerImpl.kt:141)
	at net.mamoe.mirai.console.internal.plugin.PluginManagerImpl.loadAllPluginsUsingBuiltInLoaders$mirai_console(PluginManagerImpl.kt:151)
	at net.mamoe.mirai.console.internal.MiraiConsoleImplementationBridge.doStart$mirai_console(MiraiConsoleImplementationBridge.kt:290)
	at net.mamoe.mirai.console.MiraiConsoleImplementation$Companion.start(MiraiConsoleImplementation.kt:496)
	at net.mamoe.mirai.console.terminal.MiraiConsoleTerminalLoader.startAsDaemon(MiraiConsoleTerminalLoader.kt:177)
	at net.mamoe.mirai.console.terminal.MiraiConsoleTerminalLoader.startAsDaemon$default(MiraiConsoleTerminalLoader.kt:176)
	at net.mamoe.mirai.console.terminal.MiraiConsoleTerminalLoader.main(MiraiConsoleTerminalLoader.kt:54)
Caused by: java.lang.NoClassDefFoundError: org/reflections/Configuration
	at java.base/java.lang.Class.forName0(Native Method)
	at java.base/java.lang.Class.forName(Class.java:398)
	at net.mamoe.mirai.console.internal.util.PluginServiceHelper.loadService(PluginServiceHelper.kt:51)
	... 23 more
Caused by: java.lang.ClassNotFoundException: org.reflections.Configuration
	at java.base/java.net.URLClassLoader.findClass(URLClassLoader.java:471)
	at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:588)
	at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521)
	at net.mamoe.mirai.console.internal.plugin.JvmPluginClassLoaderN.loadClass(JvmPluginClassLoader.kt:440)
	... 26 more

依赖如下：

dependencies {
    implementation("org.reflections:reflections:0.10.2")
    implementation("commons-codec:commons-codec:1.7")
    implementation("mysql:mysql-connector-java:8.0.14")


    implementation("org.quartz-scheduler:quartz:2.3.2")
    implementation("org.jsoup:jsoup:1.13.1")
    implementation("com.alibaba:fastjson:1.2.83")
    implementation("org.yaml:snakeyaml:1.25")
    implementation("org.slf4j:slf4j-api:2.0.6")

    implementation("com.zaxxer:HikariCP-java7:2.4.13")

    compileOnly("net.mamoe:mirai-core:2.14.0")
    compileOnly("net.mamoe:mirai-console:2.14.0")
}

代码如下：

@Override
    public void onEnable() {
        ConfigurationBuilder builder = new ConfigurationBuilder();
        builder.forPackage("com.pihua.plugin", this.getClass().getClassLoader());
        Reflections reflections = new Reflections(builder);

在linux上使用昨天的旧项目jar包启动，用 ./mcl > temp.log 打到文件里一看，确实是一样的异常。如果把Reflections降到0.9.10的话又将失去 builder.forPackage方法

10 replies

pilgrim773 Feb 22, 2023
Author

public final class Jar extends JavaPlugin {
public static final Jar INSTANCE = new Jar();
private Jar() {
    super(new JvmPluginDescriptionBuilder("demo.jar.mirai", "0.1.0")
            .name("Jar")
            .author("hisou")
            .build());
}

@Override
public void onEnable() {
    ConfigurationBuilder builder = new ConfigurationBuilder();
    builder.forPackage("demo.jar.mirai", this.getClass().getClassLoader());
    Reflections reflections = new Reflections(builder);


    getLogger().info("Plugin loaded!");
}
}
复现成功了，只在 java 下出现，不知道为了为什么 org.reflections.Configuration 在没使用的情况被提前加载了正常来说类信息只有 new / catch / field 等声明的时候才会被提前加载

你可以通过建立一个工具类解决
public class ERF {
    static final void load() {
        try {
            org.reflections.util.ConfigurationBuilder builder = new org.reflections.util.ConfigurationBuilder();
            builder.forPackage("demo.jar.mirai", Jar.class.getClassLoader());
            org.reflections.Reflections reflections = new org.reflections.Reflections(builder);
        } catch (Throwable cause) {
            Jar.INSTANCE.getLogger().warning("加载失败", cause);
        }
    }
}
然后在插件的主类里调用插件的主类比较特殊，最好不要在里面直接使用第三方库，因为mirai可能还没来得及为他加载

能简单解释下吗？也就是说在进入onLoad和onEnable方法之前就已经抛出这个异常了吗？
为什么套了一层工具类就可以等待mirai加载完毕它了？

cssxsh Feb 22, 2023

说在进入onLoad和onEnable方法之前就已经抛出这个异常了吗？

是的，而且代码里没有提前加载的痕迹，这可能和 new Reflections 有关（但kotlin复现不出来）
也许是某些java的优化导致了提前加载

套了一层工具类之后这个伴随初始化的加载就被移到另一个类了，所以就不会报错了

pilgrim773 Feb 22, 2023
Author

说在进入onLoad和onEnable方法之前就已经抛出这个异常了吗？

是的，而且代码里没有提前加载的痕迹，这可能和 new Reflections 有关（但kotlin复现不出来）也许是某些java的优化导致了提前加载

套了一层工具类之后这个伴随初始化的加载就被移到另一个类了，所以就不会报错了

报错是不报了，可是还是无情地加载不上类。直接写好方法，Main主类里直接调用它，size输出为 0

public class ReflectionUtil {
    public static final Set<Class<?>> getClazzListByAnnotatation() {
        try {
            org.reflections.util.ConfigurationBuilder builder = new org.reflections.util.ConfigurationBuilder();
            builder.forPackage("demo.jar.mirai", Jar.class.getClassLoader());
            org.reflections.Reflections reflections = new org.reflections.Reflections(builder);

            Set<Class<?>> classSet = reflections.getTypesAnnotatedWith(handler.class);

            System.out.println("size: " + classSet.size());

            return classSet;

        } catch (Throwable cause) {
            Jar.INSTANCE.getLogger().warning("加载失败", cause);
        }
        return null;
    }
}

包结构：

注解的生命周期为RUNTIME没有问题，反正只要dependencies里没有这句强制打包它 "shadowLink"("org.reflections:reflections")，就不给我扫描到类。
`

cssxsh Feb 22, 2023

说在进入onLoad和onEnable方法之前就已经抛出这个异常了吗？

是的，而且代码里没有提前加载的痕迹，这可能和 new Reflections 有关（但kotlin复现不出来）也许是某些java的优化导致了提前加载
套了一层工具类之后这个伴随初始化的加载就被移到另一个类了，所以就不会报错了

报错是不报了，可是还是无情地加载不上类。直接写好方法，Main主类里直接调用它，size输出为 0
public class ReflectionUtil {
    public static final Set<Class<?>> getClazzListByAnnotatation() {
        try {
            org.reflections.util.ConfigurationBuilder builder = new org.reflections.util.ConfigurationBuilder();
            builder.forPackage("demo.jar.mirai", Jar.class.getClassLoader());
            org.reflections.Reflections reflections = new org.reflections.Reflections(builder);

            Set<Class<?>> classSet = reflections.getTypesAnnotatedWith(handler.class);

            System.out.println("size: " + classSet.size());

            return classSet;

        } catch (Throwable cause) {
            Jar.INSTANCE.getLogger().warning("加载失败", cause);
        }
        return null;
    }
}
包结构：

注解的生命周期为RUNTIME没有问题，反正只要dependencies里没有这句强制打包它 "shadowLink"("org.reflections:reflections")，就不给我扫描到类。 `

再加一句 builder.addClassLoaders(Jar.class.getClassLoader());

pilgrim773 Feb 22, 2023
Author

本地测试通过，能加载出来了，晚点我再试试服务器吧。感谢
这么说forPackage并不能把类加载器给到builder么，还是得再手动add一次

尝试了一下addClassLoaders和forPackage的第二个参数都不能缺少，并不能因为add了以后就只给包名给forPackage

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

dependencies-private.txt是自己新建和填写的吗？ #2520

{{title}}

Replies: 5 comments 19 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Select a reply

dependencies-private.txt是自己新建和填写的吗？ #2520

Replies: 5 comments · 19 replies

Karlatemp Feb 21, 2023 Maintainer

pilgrim773 Feb 21, 2023 Author

pilgrim773 Feb 21, 2023 Author

pilgrim773 Feb 21, 2023 Author

pilgrim773 Feb 21, 2023 Author

pilgrim773 Feb 21, 2023 Author

pilgrim773 Feb 22, 2023 Author

pilgrim773 Feb 22, 2023 Author

pilgrim773 Feb 22, 2023 Author

pilgrim773 Feb 22, 2023 Author

pilgrim773 Feb 22, 2023 Author

pilgrim773 Feb 22, 2023 Author

Replies: 5 comments 19 replies

Karlatemp
Feb 21, 2023
Maintainer

pilgrim773 Feb 21, 2023
Author

pilgrim773
Feb 21, 2023
Author

pilgrim773 Feb 21, 2023
Author

pilgrim773 Feb 21, 2023
Author

pilgrim773
Feb 21, 2023
Author

pilgrim773 Feb 22, 2023
Author

pilgrim773 Feb 22, 2023
Author

pilgrim773
Feb 22, 2023
Author

pilgrim773 Feb 22, 2023
Author

pilgrim773 Feb 22, 2023
Author

pilgrim773 Feb 22, 2023
Author