Thanks Basil, I would definitely be interested in publishing the syslog-java-client library to Maven Central from non Jenkins project to easily consume the library.
My understanding of the Sonatype OSS publishing process is that one can only publish on a groupId he is legitimate for which probably means that the Jenkins Community will not been authorized to publish an artifact under the "com.cloudbees" groupId and will probably require to rename the groupId from "com.cloudbees" to "io.jenkins.***". Do this make sense to you? Cyrille On Wednesday, March 16, 2022 at 10:07:22 PM UTC+1 m...@basilcrow.com wrote: > Cyrille and I both now have access to this repository as members of the > syslog-java-client-developers > <https://github.com/orgs/jenkinsci/teams/syslog-java-client-developers> > group. I have updated the build to remove any CloudBees-specific parent > POMs, run CI builds on Jenkins project infrastructure, and update all > third-party dependencies. Cyrille should now be able to merge open PRs, > such as jenkinsci/syslog-java-client#50 > <https://github.com/jenkinsci/syslog-java-client/pull/50>. > > On Wed, Mar 16, 2022 at 6:49 AM 'Cyrille Le Clerc' via Jenkins Developers < > jenkin...@googlegroups.com> wrote: > > Thanks for the clarification Basil, > > I think it's still important to publish the new versions of this library > on Maven Central for all the projects outside of the Jenkins Ecosystem > that use this library. Could we evaluate solutions for this? I understand > that the Jenkins community doesn't publish artifacts to Maven Central for > the moment [1], do you have such a capability in place? > > You are correct that the Jenkins project is not currently publishing > releases to Maven Central. I do not think we would have any issue with > releasing syslog-java-client to Maven Central, but someone would need to > follow the process outlined in the Sonatype OSSRH (OSS Repository Hosting) > <https://central.sonatype.org/publish/publish-guide/> guide, including > creating a Sonatype JIRA account, filing a ticket with Sonatype to obtain > permissions (including proving ownership), and updating the Maven build to > deploy to OSSRH. Since this is not a primary use case for the Jenkins > project, I cannot volunteer my own time to complete this process, but if > Cyrille or anyone else is interested in doing this I would support their > efforts. > > If, on the other hand, we decide to use the Jenkins project's Artifactory > server, just let me know and I will add the Jenkins project parent POM and > Artifactory configuration to the build and file the usual > repository-permissions-updater > <https://github.com/jenkins-infra/repository-permissions-updater> PR for > Artifactory permissions. > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/7e87b222-8c62-4cd9-b8f0-094bc3e92f21n%40googlegroups.com.
