mirror of
https://github.com/PaperMC/Folia.git
synced 2025-04-20 19:29:18 +08:00
bc07c9f31f
The softlock would occur when a dependency tree finished executing all of its task and searched for the highest dependency tree to queue tasks from, only to have that such tree be filled with purged tasks. Because it would select an empty tree to pull tasks from, it would not select another tree to execute tasks from as this logic is done after a task is executed.
ForkTest - A Paper fork, using paperweight
This is an example project, showcasing how to setup a fork of Paper (or any other fork using paperweight), using paperweight.
The files of most interest are
- build.gradle.kts
- settings.gradle.kts
- gradle.properties
Tasks
Paperweight tasks
-----------------
applyApiPatches
applyPatches
applyServerPatches
cleanCache - Delete the project setup cache and task outputs.
createMojmapBundlerJar - Build a runnable bundler jar
createMojmapPaperclipJar - Build a runnable paperclip jar
createReobfBundlerJar - Build a runnable bundler jar
createReobfPaperclipJar - Build a runnable paperclip jar
generateDevelopmentBundle
rebuildApiPatches
rebuildPatches
rebuildServerPatches
reobfJar - Re-obfuscate the built jar to obf mappings
runDev - Spin up a non-relocated Mojang-mapped test server
runReobf - Spin up a test server from the reobfJar output jar
runShadow - Spin up a test server from the shadowJar archiveFile
Branches
Each branch of this project represents an example:
mainis the standard examplesubmodulesshows how paperweight can be applied on a fork using the more traditional git submodule systemmojangapishows how a fork could patch arbitrary non-git directories (such asPaper-MojangAPI)submodules-mojangshows the same asmojangapi, but on the git submodules setup fromsubmodules