-
Notifications
You must be signed in to change notification settings - Fork 62
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
Publish as library to maven central #118
Comments
The process to accomplish this is being started today. Thanks. |
related to #3 |
|
dlurton
added a commit
that referenced
this issue
Aug 14, 2019
This is being done in preparation for publishing to maven central. To ensure the ability to publish development versions of the library to the local maven repository for developers that do not have the GPG keys installed, we only attempt to sign the build artifacts when we are not building a "-SNAPSHOT" version.
Closed
dlurton
added a commit
that referenced
this issue
Aug 20, 2019
* Issue #118, generate pom.xml and sign build artifacts. This is being done in preparation for publishing to maven central. To preserve the ability to publish development versions of the library to the local maven repository for developers that do not have the GPG keys installed, we do not require the signing keys to be present when the `:lang:publishToMavenLocal` task is present.
Merged
PartiQL is now appearing in the maven central search results. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Are there any plans to publish as library to maven central?
The text was updated successfully, but these errors were encountered: