publishing artifact to the central maven repository #283
Conversation
alexradzin
force-pushed
the
maven-central-attempt
branch
from
341c846 to
4de747c
Compare
updated java version to 17 because it is required by plugin org.quiltmc.gradle.licenser. Source and target compatibility is still 11.
alexradzin
force-pushed
the
maven-central-attempt
branch
from
f27ddc9 to
ca53554
Compare
|
Kudos, SonarCloud Quality Gate passed!
|
There was a problem hiding this comment.
Otherwise lgtm. However, I'm thinking should we publish to both repsy and MC? Since we're trying to keep 2.* version of JDBC backwards compatible. Otherwise any existing users won't get any future updates to 2.* JDBC. We can remove repsy altogether for JDBC 3.* since that one is a major version.
| signing { | ||
| sign publishing.publications | ||
| } |
There was a problem hiding this comment.
How does signing work on github? Do we store the private key somewhere?
There was a problem hiding this comment.
yes, I have added a secret. I am planning write document on Sunday
Generally it is possible, but I do not understand why. Maven central + sonatype a standard, "default" repositories. Artefacts published there are available for any build that references it as a dependency without mentioning the repository URL. I even do not know why Repsy has been chosen and do not sure that we have to continue support it. Moreover now the group ID is changed. However this support can be restored if we really need it. |
Would users that had previously used repsy and still reference repsy in their maven config get updates to JDBC 2.*? I don't understand why are we making those changes without considering the impact.
https://packboard.atlassian.net/wiki/spaces/INTERFACES/pages/2887057554/JDBC+connector+deployment |
No description provided.