Pillar v0.6.0 — Documentation, Module Split & Maven Central
Pre-releasePillar v0.6.0 — Documentation, Module Split & Maven Central
Iteration 6 completes the public documentation and prepares the codebase for community adoption by strictly separating the API contracts from the implementation. It enforces a hard physical boundary, ensuring pure API contracts with zero external dependencies, and officially publishes the artifact to Maven Central for direct consumer consumption.
Architecture & Distribution
- Module Split — Enforced a hard architectural boundary via Gradle. The project is now separated into two physical subprojects:
pillar-apicontaining pure Java API contracts (with no external dependencies other than the JDK), andpillar-pluginhousing the implementations, shading, and platform adapters. - Maven Central Publication — The
pillar-apiartifact is now formally published to Maven Central. Plugin developers can now securely depend on the API contracts using standard dependency managers (Gradle/Maven) without relying on custom repository definitions.
Documentation & Community
- Public Documentation — Launched an extensive documentation site at pillar.markineo.com.br, built with Starlight. It features comprehensive architecture overviews, detailed developer cookbooks, and a structured getting-started guide.
- Internationalization (i18n) — Full documentation support established for English (EN), Spanish (ES), and Brazilian Portuguese (PT-BR), heavily audited to ensure native software engineering taxonomy across all supported languages.
API Hardening
- Lease API Minimization — Reduced the public surface area of the
LeaseServiceby explicitly removingOwnerTokenexposures from theLeaserecord. The fencing token is now handled implicitly by internal systems, relying entirely on atomic Redis Lua script fencing to guarantee absolute safety without leaking implementation details to consumers.
Upgrading from 0.5.0
Drop-in replacement for server administrators. No breaking configuration changes. Requirements remain unchanged: Paper 26.1.2 and/or Velocity 3.4.0, Java 25, Redis 7.
Plugin developers must update their build scripts to depend on the newly published pillar-api artifact from Maven Central, utilizing compileOnly (Gradle) or the provided scope (Maven).
What's next (Iteration 7 — Marketing & Outreach)
Iteration 7 will focus on launch and community adoption, targeting small and medium networks. Work will encompass publishing the plugin to major platforms (Modrinth, Hangar, SpigotMC, Polymart) and executing a structured, culturally adapted outreach strategy across the pt-BR, EN, and ES communities.