Mirror von
https://github.com/PaperMC/Paper.git
synchronisiert 2024-11-14 20:10:05 +01:00
b6cf80ee66
This is for 2 reasons: 1) Ensuring our log4j is mostly loaded at OUR version. I've seen stack traces with line numbers that do not match our version. This means that some plugin has shaded in log4j and their loaded version is mixing with ours.... So by at least trying to load a bunch of log4j classes before we load plugins, we can be more sure mixed versions are not loading. 2) If the jar file is replaced while the server is runnimg class not found errors galore This will preloaod a bunch of classes commonly seen to error during shutdown due to this. The goal here is to help let the server shutdown gracefully as possible. Some plugins will still blow up here if they access a class that hadn't been loaded yet, but goal is to at least stop freezing the shutdown process as it does with JLine and Log4j errors requiring an external kill. Ideally you should not replace jars while the server is running, but it is something that happens in development for testing. Updated test server to do a copy though to avoid this happening in Paper development. |
||
|---|---|---|
| .. | ||
| pre-source-patches | ||
| apatch.sh | ||
| applyPatches.sh | ||
| build.sh | ||
| checkoutpr.sh | ||
| decompile.sh | ||
| functions.sh | ||
| importmcdev.sh | ||
| init.sh | ||
| makemcdevsrc.sh | ||
| paperclip.sh | ||
| rebuildPatches.sh | ||
| remap.sh | ||
| testServer.sh | ||
| upstreamCommit.sh | ||
| upstreamMerge.sh | ||