Problems with dependencies still being included in class path about plugin-yml HOT 6 CLOSED

1. You need to set the loader class in the paper { ... } block.

2. I'm not sure. This part is a bit suspicious and looks like it would include classes from dependencies in your plugin JAR. Why do you need it? Same for the shadow plugin.

   tasks.jar {
     val dependencies = configurations
         .runtimeClasspath
         .get()
         .map(::zipTree)
     from(dependencies)
     duplicatesStrategy = DuplicatesStrategy.EXCLUDE
   }

   If you want to use the library mechanism you shouldn't need any of this.

   It doesn't fully explain the problem though. kotlin-stdlib shouldn't actually end up in the runtimeClasspath, since library should be a compileOnly dependency. Maybe check ./gradlew :dependencies to get a list of dependencies and see if kotlin is actually on the runtimeClasspath and why.

from plugin-yml.

Thx for your quick response, the second issue has been solved. It seems like I copied the code snippet in at sometime and then just categorically overlooked it. Removing it solved the issue.

I've referenced my main class as loader in paper, the same class that is also named under paper.main. But at plugin startup the server doesn't find the kspigot class:
[EntrypointUtil] net/axay/kspigot/main/KSpigot java.lang.NoClassDefFoundError: net/axay/kspigot/main/KSpigot

And it is also not downloaded in the libraries folder in the server directory. But it referenced in the paper-libraries.json in the jar.

from plugin-yml.

You need to create a custom PluginLoader class, see https://github.com/Minecrell/plugin-yml#paper-1 ("Example PluginLoader").

In many cases it might be easier to declare a bukkit { ... } plugin instead. In that case you don't need a PluginLoader because Bukkit/Spigot plugins can declare libraries in plugin.yml. You can still use most of the Paper-specific API from a good old Bukkit/Spigot plugin.

Personally I would suggest using a Paper plugin only if you are sure that you can benefit from the new/extra functionality offered by those.

from plugin-yml.

Okay, yes replacing pluginYml for Paper with the bukkit version solved the issue for me. Thx a whole lot!
But how can I add my own libraries that are not on maven central? I've tried to shade them into the plugin using shadow. But everytime I use shadow the kotlin libraries and a whole lot more get included again.

from plugin-yml.

But how can I add my own libraries that are not on maven central?

In this case you could either use a custom PluginLoader for a Paper plugin, which would let you configure additional Maven repositories (see resolver::addRepository) in the example I linked.

I've tried to shade them into the plugin using shadow. But everytime I use shadow the kotlin libraries get included again.

Well, it's still not clear to me why you have kotlin on the runtimeClasspath used by shadow (see my first comment). It would be good to figure out why that happens, but you could also explicitly include only the dependencies you want (see https://imperceptiblethoughts.com/shadow/configuration/dependencies/#filtering-dependencies).

from plugin-yml.

Thanks a lot for your help! I was able to shade the required dependency into the plugin using:

tasks.shadowJar {
        dependencies {
            include(<My Dependency>)
        }
}

from plugin-yml.