-
Notifications
You must be signed in to change notification settings - Fork 3
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
migrate to maven-central publishing #39
Comments
OSSRH-64213 created. |
DNS settings updated |
Tried to sync one of the existing artifacts but our released artifacts don't appear to be valid for maven central.
|
Yes, the Maven Central is slightly more demanding than Bintray. You would need to tweak up your project configuration to handle that for your new artifacts. Here's a repo that can help you: Or you can wait a liitle bit to have it updates to the brand new https://github.com/gradle-nexus/publish-plugin/ which makes it even easier. In the meantime, a separate migration guide (from the GNSP + NPP duo): |
- update to kotlin 1.4.20 (align with Kotlin version in Gradle) to get rid of build warning. - add dokka to generate javadoc artifacts (required by maven central) - added additional plugins to make releasing to maven-central completely automatic. - added signing plugin (conditionally on signing project property to be available). - add required information to poms for all maven publications. - moved plugin version management into Gradle settings file.
Done a first (manual) release of kuberig-dsl to maven-central with a 1.5.0-RC1 version number. Staged repository has been released and dropped so waiting for the sync. |
dokka and some of it's transitive dependencies are not available on maven-central so had to keep jcenter in for the moment. I've added group limits for jcenter. In the mean time we need to keep track of the dokka issue for progress on this: Kotlin/dokka#41. |
after the release hits maven central I can have a look on the kuberg-dsl-kubernetes / kuberig-dsl-openshift projects and the kuberig-dsl-vanilla-gradle plugin that is used in these projects. after that is done kuberig itself is up. |
- provide signing details to build
@szpak ok I feel exceptionally stupid, spending way too much time on this. Just doesn't want to work in the CI jobs, always results in a 401 when trying to create the staging profile. While locally it just works even when I exec into the gitlab runner container and execute manually it works. tried the following without success:
|
ok just tested the staging repo create with a custom task and it works in the job. Didn't change anything on the environment variables... |
As jcenter is shutting down we need to replace our jcenter publishing with maven-central publishing
The text was updated successfully, but these errors were encountered: