PAR-268
0
Prune a plugin's own stale staged jars in copyPlugin so server/plugins doesn't accumulate old versions
Pending ReleaseUnassignedTreasury
copyPlugin (treasury, business, treasury-api-plugin) used layout.projectDirectory.dir("../../server/plugins"), which from a top-level subproject climbs treasury → hibernia-economy → workspace and writes to C:\Users\rian\workspace\server\plugins — outside the repo, not the in-repo server/plugins the wiki/CLAUDE.md describe. As a Copy, it also never pruned old versions.
Fixed:
- Corrected the path to
../server/plugins(the documented in-repo dev server) in all three plugin builds. - Before copying, delete only this artifact's previously-staged jars, matched on its own base name + a version digit (
^treasury-\d.*\.jar$, sotreasurynever matchestreasury-api-plugin). Sibling plugins (LuckPerms/WorldEdit/WorldGuard/ChestShop) and data folders are left untouched.
Verified: :treasury:copyPlugin now stages treasury-2.3.0 into the in-repo server, prunes treasury-2.2.1, and leaves every other jar and data folder intact.
Leftover: the old buggy path created a stray C:\Users\rian\workspace\server\plugins outside the repo (can be deleted).
Resources
- commit8332ff2 Stage plugins into the in-repo server/plugins and prune stale jars (PAR-268)ParadauxIO/hibernia-economy
Comments
No comments yet.
Activity
- ParadauxIO linked a commit — Commit 8332ff2 — Stage plugins into the in-repo server/plugins and prune stale jars (PAR-268)
- tesks description: Description updated
- tesks changed status to Status → Pending Release
- tesks created the issue