Repository navigation
chore: Stop publishing swagger-validator WAR to Maven Central - #295
Merged
Merged
Conversation
There was a problem hiding this comment.
🟡 Changes recommended
The release workflow still lacks the Maven build needed to generate the JAR and WAR files that the subsequent Docker build copies, so releases will fail on fresh runners.
1 open issue
What changed in this PR
This pull request stops publishing the single-module WAR to Maven Central and makes the Docker image the project’s release artifact.
Changes:
- Removes Maven Central publishing, signing, source, and Javadoc configuration from
pom.xml. - Removes Maven deployment credentials and deploy steps from GitHub Actions workflows.
- Updates README and CI documentation to describe Docker-based releases and local WAR builds.
| File | Description |
|---|---|
| README.md | Documents the discontinuation of Maven Central publication and directs users to Docker or local source builds. |
| pom.xml | Removes Maven Central publishing, GPG signing, source JAR, and Javadoc JAR configuration. |
| CI/CI.md | Updates CI and release documentation to reflect Docker-only publishing. |
| .github/workflows/release.yml | Removes Maven Central credentials and release deployment steps. |
| .github/workflows/prepare-release.yml | Removes obsolete Maven Central setup and credentials. |
| .github/workflows/maven.yml | Changes master CI from snapshot deployment to Maven package verification. |
| .github/workflows/maven-pulls.yml | Removes unused Maven Central setup from pull-request CI. |
Review effort: Lite
ewaostrowska
force-pushed
the
remove-war
branch
from
November 19, 2026 13:27
a658d42 to
7826404
Compare
djankows
approved these changes
Nov 19, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

io.swagger.validator.v3:swagger-validatoris a WAR. The Docker imageswaggerapi/swagger-validator-v2is the real release artifact, so the Maven Central publish (snapshots on every master push, releases via GPG signing) is no longer needed.Why the whole deploy is removed, unlike swagger-codegen #12783
swagger-codegen #12783 kept the Central deploy and only excluded one artifact. It added
<excludeArtifact>swagger-generator</excludeArtifact>tocentral-publishing-maven-pluginand a README note. That works there because codegen is a multi-module build. Theswagger-generatorWAR is one module among several libraries (such as codegen and the CLI) that still need to be published.validator-badge is a single-module project with
packaging=war. Its only Maven artifact is the WAR, plus the sources jar, javadoc jar and POM that exist only to satisfy Central. Excluding the WAR would leave a deploy that publishes nothing. So the whole chain is removed instead:deploy,-Prelease deploystep,