paperweight
paperweight copied to clipboard
PaperMC
Gradle build system plugin for Paper and Paper forks
Patch sets would have properties which define how they are applied and what they are etc. Example config in Kotlin I came up with on the fly: ```kotlin patchSets {...
tried it here https://github.com/PaperMC/paperweight/tree/feature/importmcdev obviously doesn't work, because the files will not be added to git at the right spot. maybe we wanna automate stashing and then do a fixup...
``` > Task :paper:Paper-API:jar Execution optimizations have been disabled for task ':paper:Paper-API:jar' to ensure correctness due to the following reasons: - Gradle detected a problem with the following location: 'D:\IntellijProjects\ForkTest\.gradle\caches\paperweight\upstreams\paper\Paper-API\build\classes\java\main'....
It is currently impossible to maintain a fork pre 1.17 with this because of the forced mojmap steps. It would be nice to have a setting to disable just those...
For simplicity and to just get paperweight working I have dependencies downloading in tasks using a download service that I copied from the download-task plugin. This works fine but isn't...
Rebuild patches task sends all paper commits to the patches folder I just want my commits to come. but the upstream commits are coming, too. build.gradle.kts: https://hastebin.com/efejamubeb.kotlin gradle.properties: https://hastebin.com/foyamaqofa.properties settings.gradle.kts:...
Removes need to special case api & mojangapi, keeps versions in sync, and allows more flexibility for including own project dependencies (forks) closes #162 known issue: Included project dependency sources...
not sure if this right place to ask questions but, got question regarding paperweight-patcher for some reason `generateDevBundle` jar is ignoring subproject like this `implementation(project(:SubProject))`, which when inspecting `config.json` of...
While trying to find out why hot reloading single classes takes "ages", I found out, that when Gradle is no longer forced to recompile everything (through the log4j2 annotation processor)...
Check registry and git configs to see if long paths are likely to be a problem, and print a warning if so.