Skip to content

Keep runtime deps in published POM; auto-publish to Maven Central #28

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jochen-testingbot merged 1 commit into from
Jul 15, 2026
Merged

Keep runtime deps in published POM; auto-publish to Maven Central #28

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions pom.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -77,6 +77,10 @@
<extensions>true</extensions>
<configuration>
<publishingServerId>central</publishingServerId>
<!-- Actually release to Maven Central instead of leaving the deployment in a
"pending/validated" state that needs a manual "Publish" click in the portal. -->
<autoPublish>true</autoPublish>
<waitUntil>published</waitUntil>
</configuration>
</plugin>
<plugin>
Expand Down Expand Up @@ -152,6 +156,11 @@
The runnable uber jar is attached under the "shaded" classifier for CLI/Docker use. -->
<shadedArtifactAttached>true</shadedArtifactAttached>
<shadedClassifierName>shaded</shadedClassifierName>
<!-- Keep the real dependencies in the published POM. Because the uber jar is only an
attached artifact (not the main one), the main jar is thin and its consumers must
resolve Jetty/HTTP/commons-cli/etc. transitively; the default dependency-reduced
POM would strip exactly those and leave consumers with unresolvable classes. -->
<createDependencyReducedPom>false</createDependencyReducedPom>
<minimizeJar>true</minimizeJar>
<filters>
<filter>
Expand Down
Loading