Slackbot
11/28/2023, 8:44 AMephemient
11/28/2023, 8:56 AMpluginManager.apply(...) instead of plugin.apply(...)ephemient
11/28/2023, 8:58 AMChristoph Hermann
11/28/2023, 9:45 AMChristoph Hermann
11/28/2023, 9:45 AMVampire
11/28/2023, 10:10 AMproject.apply(...) 😄
But either way will most probably not change any problems you might have as these methods of applying do not influence class loaders.Vampire
11/28/2023, 10:13 AMcompileOnly dependencies on those plugins and then apply your plugin in the root project but the other plugin only in a subproject, then your plugin cannot access the plugins classes as they are on a classloader lower in the hierarchy.Christoph Hermann
11/28/2023, 10:31 AMChristoph Hermann
11/28/2023, 10:32 AMVampire
11/28/2023, 10:33 AMmaven-publish if you can. 🙂Christoph Hermann
11/28/2023, 10:35 AMthis.project.getPlugins().apply(pluginId); and this.project.getPluginManager().withPlugin(id, action);
Should we align this to always use the pluginmanager?Vampire
11/28/2023, 10:37 AMproject.getPlugins(), that should make it clear. 🙂
If not, feel free to ask again.Vampire
11/28/2023, 10:38 AMChristoph Hermann
11/28/2023, 10:39 AM