I'm developing multi-module paper project.
In original paperweight I could just use this in root project:
alias(libs.plugins.paper) apply false
...
// apply kotlin plugin in all subprojects
And this in subprojects:
plugins {
alias(libs.plugins.paper)
}
dependencies {
paperweight.paperDevBundle(libs.versions.bukkit)
}
libs.versions.toml:
[versions]
kotlin = "2.3.10"
minecraft = "1.21"
bukkit = "1.21.11-R0.1-SNAPSHOT"
[plugins]
kotlin = { id = "org.jetbrains.kotlin.jvm", version.ref = "kotlin" }
paper = "io.papermc.paperweight.userdev:2.0.0-beta.19"
But in weaver userdev + horizon it's a build error
It requires dev bundle in root project.
Also, can paper-plugin.yml generator be used along weaver userdev and horizon?
https://docs.eldoria.de/pluginyml/paper/
Another question for me is how do I properly split horizon and paper sources in hybrid plugins?
In root project:
plugins {
alias(libs.plugins.kotlin)
}
tasks.jar { enabled = false }
subprojects {
...
sourceSets.main {
kotlin.srcDir("src")
resources.srcDir("resources")
}
...
}
And last question. Will horizon server load horizon and paper plugin from one jar file? (hybrid plugin)
I'm developing multi-module paper project.
In original paperweight I could just use this in root project:
And this in subprojects:
libs.versions.toml:
But in weaver userdev + horizon it's a build error
It requires dev bundle in root project.
Also, can paper-plugin.yml generator be used along weaver userdev and horizon?
https://docs.eldoria.de/pluginyml/paper/
Another question for me is how do I properly split horizon and paper sources in hybrid plugins?
In root project:
And last question. Will horizon server load horizon and paper plugin from one jar file? (hybrid plugin)