Skip to content

Update publishing-java-packages-with-gradle.md #8049

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
lecoursen merged 5 commits into from
Aug 31, 2021
Merged

Update publishing-java-packages-with-gradle.md #8049

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
12e5111
Update publishing-java-packages-with-gradle.md
mahozad Jul 9, 2021
233a052
Fix another incorrect name in the code
mahozad Jul 10, 2021
bbe3357
Add :nail_care:
lecoursen Aug 31, 2021
9fc88b1
Use product name variable
lecoursen Aug 31, 2021
4e21d05
Merge branch 'main' into patch-2
lecoursen Aug 31, 2021
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
10 changes: 4 additions & 6 deletions content/actions/guides/publishing-java-packages-with-gradle.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -74,9 +74,7 @@ publishing {
```
{% endraw %}

With this configuration, you can create a workflow that publishes your package to the Maven Central Repository by running the `gradle publish` command. You’ll also need to provide environment variables that contain the username and password to authenticate to the repository.

In the deploy step, you’ll need to set environment variables for the username and password or token that you use to authenticate to the Maven repository. For more information, see "[Creating and using encrypted secrets](/github/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)."
With this configuration, you can create a workflow that publishes your package to the Maven Central Repository by running the `gradle publish` command. In the deploy step, you’ll need to set environment variables for the username and password or token that you use to authenticate to the Maven repository. For more information, see "[Creating and using encrypted secrets](/github/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)."

```yaml{:copy}
{% data reusables.actions.actions-not-certified-by-github-comment %}
Expand Down Expand Up @@ -143,7 +141,7 @@ publishing {
```
{% endraw %}

With this configuration, you can create a workflow that publishes your package to the Maven Central Repository by running the `gradle publish` command.
With this configuration, you can create a workflow that publishes your package to {% data variables.product.prodname_registry %} by running the `gradle publish` command.

```yaml{:copy}
{% data reusables.actions.actions-not-certified-by-github-comment %}
Expand Down Expand Up @@ -185,7 +183,7 @@ Ensure your _build.gradle_ file includes a repository for both your {% data vari

For example, if you deploy to the Central Repository through the OSSRH hosting project, you might want to specify it in a distribution management repository with the `name` set to `OSSRH`. If you deploy to {% data variables.product.prodname_registry %}, you might want to specify it in a distribution management repository with the `name` set to `GitHubPackages`.

If your organization is named "octocat" and your repository is named "hello-world", then the {% data variables.product.prodname_registry %} configuration in _build.gradle_ would look similar to the below example.
If your organization is named "octocat" and your repository is named "hello-world", then the configuration in _build.gradle_ would look similar to the below example.

{% raw %}
```groovy{:copy}
Expand Down Expand Up @@ -243,7 +241,7 @@ jobs:
distribution: 'adopt'
- name: Validate Gradle wrapper
uses: gradle/wrapper-validation-action@e6e38bacfdf1a337459f332974bb2327a31aaf4b
- name: Publish to the Maven Central Repository
- name: Publish package
run: gradle publish
env: {% raw %}
MAVEN_USERNAME: ${{ secrets.OSSRH_USERNAME }}
Expand Down