> Hi Cyrille, On Tue, Mar 29, 2022 at 11:02 PM Basil Crow <[email protected]> wrote: > Based on my reading of the Sonatype documentation, I think your > understanding is correct, but I would not necessarily assume that the > use of the "com.cloudbees" namespace by the Jenkins project for such > legacy libraries is forbidden. I think that is an open question that > we could pose to CloudBees management, and in particular Michaël > Pailloncy (who started this discussion). Non-technical matters aside, > the technical cost to CloudBees would be small (assisting with > Sonatype verification), while the technical benefit to users would be > large (avoiding a migration of Maven group ID for all consumers of > this library), so I think it is at least worth asking. If the answer > is no, fine - we can switch the group ID to "io.jenkins", open a help > desk ticket with the Jenkins infrastructure team to assist with the > Sonatype verification, and ask all downstream consumers to change > group IDs. I have no strong preference either way.
Based on the lack of a response, I am assuming the answer to this question was a "no." So would you like to proceed with publishing syslog-java-client under a new set of Maven coordinates? We currently have these two namespaces approved for publishing to Maven Central: - io.jenkins.archetypes - io.jenkins.tools I propose we create a new namespace: io.jenkins.syslog If this is OK with you, I can create the new namespace in the Central Portal and publish it to Central under the new coordinates. Thanks, Basil -- 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 [email protected]. To view this discussion visit https://groups.google.com/d/msgid/jenkinsci-dev/CAFwNDjqoo%2BFF-oQNTV%3DAv8bpwFUmCTT6g02H69n8CLbYDUC7kQ%40mail.gmail.com.
