docs: complete plugin foundation story
This commit is contained in:
@@ -20,3 +20,9 @@ description: Chronological record of material decisions affecting Spigot Quest B
|
|||||||
## 2026-09-05 — Foundation started
|
## 2026-09-05 — Foundation started
|
||||||
|
|
||||||
- Approved work begins with an OKF knowledge bundle, Java 25/Purpur 26.2 Gradle foundation, automated verification, and a public Gitea repository.
|
- Approved work begins with an OKF knowledge bundle, Java 25/Purpur 26.2 Gradle foundation, automated verification, and a public Gitea repository.
|
||||||
|
|
||||||
|
## 2026-09-05 — Foundation completed
|
||||||
|
|
||||||
|
- Published the project to the public `dmg/spigot-quest-board` Gitea repository.
|
||||||
|
- Added strict Java 25/Purpur 26.2 Gradle builds, plugin metadata, a metadata regression test, and CI/release workflows modeled on Spigot Base.
|
||||||
|
- Verified the plugin foundation and JAR with `./gradlew clean check jar`.
|
||||||
|
|||||||
@@ -2,7 +2,7 @@
|
|||||||
type: User Story
|
type: User Story
|
||||||
title: "US-001: Build and release the plugin"
|
title: "US-001: Build and release the plugin"
|
||||||
description: Give maintainers repeatable Purpur builds, automated verification, and versioned public Gitea releases.
|
description: Give maintainers repeatable Purpur builds, automated verification, and versioned public Gitea releases.
|
||||||
status: in-progress
|
status: done
|
||||||
---
|
---
|
||||||
|
|
||||||
# US-001: Build and release the plugin
|
# US-001: Build and release the plugin
|
||||||
@@ -11,17 +11,17 @@ As a **plugin maintainer**, I want automated builds and releases modeled on Spig
|
|||||||
|
|
||||||
## Acceptance criteria
|
## Acceptance criteria
|
||||||
|
|
||||||
- [ ] The Gradle project compiles against Purpur API `26.2.build.2618-stable` using a Java 25 toolchain.
|
- [x] The Gradle project compiles against Purpur API `26.2.build.2618-stable` using a Java 25 toolchain.
|
||||||
- [ ] Compiler lint warnings fail the build.
|
- [x] Compiler lint warnings fail the build.
|
||||||
- [ ] Automated JUnit 5 tests run as part of the Gradle check lifecycle.
|
- [x] Automated JUnit 5 tests run as part of the Gradle check lifecycle.
|
||||||
- [ ] Plugin metadata declares the entrypoint, player and admin commands, and permissions.
|
- [x] Plugin metadata declares the entrypoint, player and admin commands, and permissions.
|
||||||
- [ ] Pushes and pull requests build and test the plugin in Gitea Actions.
|
- [x] Pushes and pull requests build and test the plugin in Gitea Actions.
|
||||||
- [ ] Pull requests validate conventional commit messages.
|
- [x] Pull requests validate conventional commit messages.
|
||||||
- [ ] CI stores a development JAR as a workflow artifact.
|
- [x] CI stores a development JAR as a workflow artifact.
|
||||||
- [ ] Main-branch conventional commits drive semantic versioning.
|
- [x] Main-branch conventional commits drive semantic versioning.
|
||||||
- [ ] A successful release builds a versioned JAR and attaches it to the corresponding Gitea release.
|
- [x] A successful release builds a versioned JAR and attaches it to the corresponding Gitea release.
|
||||||
- [ ] The project is published in the public `dmg/spigot-quest-board` Gitea repository.
|
- [x] The project is published in the public `dmg/spigot-quest-board` Gitea repository.
|
||||||
- [ ] Build files, Gradle wrapper, workflows, and release behavior follow `../spigot-base/` where applicable while using Spigot Quest Board names and identifiers.
|
- [x] Build files, Gradle wrapper, workflows, and release behavior follow `../spigot-base/` where applicable while using Spigot Quest Board names and identifiers.
|
||||||
|
|
||||||
## Related
|
## Related
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user