Publish Maven artifacts to dogtagpki/repo #4798
Merged
Conversation
This file contains 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
Previously PKI's Maven artifacts were published to GitHub Packages which is a private repository so it's difficult to use. To resolve the problem, the pom.xml has been modified to publish the artifacts to a publicly accessible dogtagpki/repo instead.
|
|
@fmarco76 Thanks! |
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.
Previously PKI's Maven artifacts were published to GitHub Packages which is a private repository so it's difficult to use.
To resolve the problem, the
pom.xmlhas been modified to publish the artifacts to a publicly accessible dogtagpki/repo instead.The build job in the publish action will use JSS and LDAP SDK artifacts already in that repo: /dogtagpki/repo/tree/maven. In the future all build jobs in the CI should be updated to use that repo as well.