Maven archetype that generates a structured multi-module Java service app and optionally using Spring Boot with integration, service, and presentation architectural tiers.
Describe the application’s integrations, service areas, and presentation architectural tiers at generation time; the archetype builds the full module tree and wires up all POMs.
mvn archetype:generate \
-DarchetypeGroupId=io.github.jeffjensen \
-DarchetypeArtifactId=java-service-archetype \
-DarchetypeVersion=VERSIONReplace VERSION with the archetype release you want to use.
See the project site for the full prompts reference, module structure, examples, and build instructions.
Four GitHub Actions workflows are included.
Runs ./mvnw clean verify on every push and pull request.
Documentation-only changes (.adoc, .md, src/site/**) are skipped — those pushes trigger the site publish directly instead.
Triggered when the build workflow succeeds on main.
Publishes a -SNAPSHOT artifact to Maven Central (Sonatype).
Release versions (without -SNAPSHOT) are skipped automatically.
Required repository secrets:
| Secret | Description |
|---|---|
|
Maven Central portal username |
|
Maven Central portal token |
Triggered when maven-release-plugin pushes a v* tag.
Runs in a release environment and deploys a GPG-signed release to Maven Central via ./mvnw deploy -Prelease.
See the Releasing guide for the full procedure and one-time setup.
Required repository secrets, in addition to CENTRAL_USERNAME and CENTRAL_TOKEN above:
| Secret | Description |
|---|---|
|
ASCII-armored GPG private key for artifact signing |
|
Passphrase for the signing key |
Triggered in three ways: when the build workflow succeeds on main; on any direct push to main that touches doc files (.adoc, .md, src/site/**); or manually via workflow_dispatch.
Runs ./mvnw site and publishes the Maven site to GitHub Pages.
Enable GitHub Pages (repository Settings → Pages → Source: GitHub Actions) before the first run.