Produce shaded Bukkit plugin jar for Purpur 1.19.4 and bundle/relocate dependencies #1

2026-03-13T09:40:57-04:00

NotAlexNoyle commented

2026-03-13 09:40:57 -04:00

(Migrated from github.com)

Motivation

The packaged plugin produced an invalid tiny JAR instead of a server-loadable shaded artifact, so bundled libraries were not included or relocated.
The Bukkit module must target Purpur 1.19.4 and avoid runtime conflicts by shading/relocating third-party libs like bStats.
Build output should place the final server-ready plugin JAR in build/libs where CI and users expect it.

Description

Switches the Bukkit API to Purpur by adding the Purpur snapshots repository and using org.purpurmc.purpur:purpur-api:1.19.4-R0.1-SNAPSHOT in bukkit/build.gradle.kts.
Configures shadowJar to be the primary plugin artifact by setting archiveClassifier.set(""), enabling relocation, and relocating org.bstats into the plugin-specific namespace ${project.group}.${rootProject.name.lowercase()}.lib.bstats.
Updates root build.gradle.kts to apply the Shadow plugin to subprojects, set reproducible archive settings (isPreserveFileTimestamps and isReproducibleFileOrder), enable default Shadow relocation (isEnableRelocation and relocationPrefix), and set archiveFileName for shadow outputs.
Disables the empty root jar and adds a Sync task pluginArtifact that depends on :Chunky-bukkit:shadowJar and copies that shadow JAR into the root build/libs directory so a server-ready plugin JAR is produced where expected.

Testing

Ran ./gradlew :Chunky-bukkit:shadowJar with JAVA_HOME set to a Java 17 toolchain, and the build failed due to external plugin resolution errors when fetching the Shadow Gradle plugin from remote repositories (HTTP 403), so the local environment could not complete the build.
Earlier attempts used ./gradlew clean build -x test and --stacktrace to gather diagnostics and confirmed the failure was due to plugin resolution rather than project configuration errors.

Codex Task

### Motivation - The packaged plugin produced an invalid tiny JAR instead of a server-loadable shaded artifact, so bundled libraries were not included or relocated. - The Bukkit module must target Purpur 1.19.4 and avoid runtime conflicts by shading/relocating third-party libs like bStats. - Build output should place the final server-ready plugin JAR in `build/libs` where CI and users expect it. ### Description - Switches the Bukkit API to Purpur by adding the Purpur snapshots repository and using `org.purpurmc.purpur:purpur-api:1.19.4-R0.1-SNAPSHOT` in `bukkit/build.gradle.kts`. - Configures `shadowJar` to be the primary plugin artifact by setting `archiveClassifier.set("")`, enabling relocation, and relocating `org.bstats` into the plugin-specific namespace `${project.group}.${rootProject.name.lowercase()}.lib.bstats`. - Updates root `build.gradle.kts` to apply the Shadow plugin to subprojects, set reproducible archive settings (`isPreserveFileTimestamps` and `isReproducibleFileOrder`), enable default Shadow relocation (`isEnableRelocation` and `relocationPrefix`), and set `archiveFileName` for shadow outputs. - Disables the empty root `jar` and adds a `Sync` task `pluginArtifact` that depends on `:Chunky-bukkit:shadowJar` and copies that shadow JAR into the root `build/libs` directory so a server-ready plugin JAR is produced where expected. ### Testing - Ran `./gradlew :Chunky-bukkit:shadowJar` with `JAVA_HOME` set to a Java 17 toolchain, and the build failed due to external plugin resolution errors when fetching the Shadow Gradle plugin from remote repositories (HTTP 403), so the local environment could not complete the build. - Earlier attempts used `./gradlew clean build -x test` and `--stacktrace` to gather diagnostics and confirmed the failure was due to plugin resolution rather than project configuration errors. ------ [Codex Task](https://chatgpt.com/codex/tasks/task_e_69b4124aeaec832fb4c470f3050f9c37)

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: trueog/Chunky#1