Skip to content
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

Jump to bottom

Patch 1 #77

Open
wants to merge 2 commits into
base: development
Choose a base branch
from
Open

Patch 1 #77

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
8fc5125
Explain different Maven upload flows
FDelporte Jul 29, 2024
1a5f41d
Add link to PGP post
FDelporte Jul 29, 2024
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
11 changes: 9 additions & 2 deletions docs/modules/examples/pages/maven/maven-central.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -27,7 +27,14 @@ You have the option to close and release the staged repository automatically rig
repository open and perform close and release operations using the UI. You must login into Sonatype OSSRH using your
Sonatype account to do so.

== Portal Publisher API
== Different Work-flows

The Maven project has a long history and is going through some evolutions to create, upload, manage, and use Java libraries. As a result, there are two approaches to publish artifacts to the repository:

- Traditional OSSRH way, also known as the Maven Central Nexus Repository. The UI can be accessed via https://oss.sonatype.org.
- New API approach via the Maven Central Repository, creating a login and managing your artifacts can be done via https://central.sonatype.com/

=== Portal Publisher API

Publishing using the Portal Publisher API requires using the xref:reference:deploy/maven/maven-central.adoc[] deployer.

Expand Down Expand Up @@ -150,7 +157,7 @@ jreleaser {
--
====

== OSSRH
=== OSSRH

Publishing to OSSRH requires using the xref:reference:deploy/maven/nexus2.adoc[] deployer.

Expand Down
2 changes: 1 addition & 1 deletion docs/modules/reference/pages/signing.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ Signing ensures that the artifacts have been generated by yourself and your user
generated signature with your public signing key.

JReleaser can sign all files, including distribution archives and any extra files attached to the project. This section
must be configured if you intend to sign commits as well. You may sign using PGP or link:https://www.sigstore.dev/[Sigstore]'s cosign.
must be configured if you intend to sign commits as well. You may sign using PGP (as described in link:https://maciejwalkowiak.com/blog/publish-java-library-maven-central/#_3-create-gpg-keys[this post by Maciej Walkowiak]) or link:https://www.sigstore.dev/[Sigstore]'s cosign.

Use the following options to customize how files may be signed:

Expand Down