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.

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

Build the library using github actions and publish to maven central #3

Open
allanmoso opened this issue Oct 6, 2021 · 4 comments · May be fixed by #17
Open

Build the library using github actions and publish to maven central #3

allanmoso opened this issue Oct 6, 2021 · 4 comments · May be fixed by #17

Comments

@allanmoso
Copy link
Collaborator

This repo is currently not yet published to maven central. We would like to build this repo using GitHub actions and publish the artifact to maven central.

@allanmoso
Copy link
Collaborator Author

allanmoso commented Oct 7, 2021

@dbirks There are some changes in PR #9 that added changes that allows us to publish to Maven Central approved repo (Sonatype). See https://github.com/egineering-llc/salesforce-oauth/blob/main/release.md

@allanmoso
Copy link
Collaborator Author

@dbirks I added the secrets for all of the environment variables described in this guide: https://github.com/actions/setup-java/blob/main/docs/advanced-usage.md#publishing-using-apache-maven

The secrets are named:
MAVEN_CENTRAL_TOKEN
MAVEN_GPG_PASSPHRASE
MAVEN_GPG_PRIVATE_KEY
MAVEN_USERNAME

@dbirks
Copy link
Member

dbirks commented Oct 7, 2021

Cool! GPG too 🙂

I'll work on a PR to add that today or tomorrow.

And I'll have to play with it on my fork, but I may end up splitting up the mvn release command to do one commit at a time, and do a git push in between each step. That way there'll be multiple pushes, triggering multiple publishes.

Thank you, lots of new stuff to me, I'll take a look.

@dbirks dbirks linked a pull request Oct 27, 2021 that will close this issue
@dbirks
Copy link
Member

dbirks commented Oct 27, 2021

Better late than never... opened #17 to run the mvn release command. Also making it manually-triggered only.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants