Keeping the same groupId would definitively be the best solution. Let's see 
what's CloudBees' answer.

Cyrille
On Wednesday, March 30, 2022 at 8:02:43 AM UTC+2 [email protected] wrote:

> Hi Cyrille,
>
> On Wed, Mar 23, 2022 at 3:39 AM 'Cyrille Le Clerc' via Jenkins
> Developers <[email protected]> wrote:
> > I would definitely be interested in publishing the syslog-java-client 
> library to Maven Central from non Jenkins project to easily consume the 
> library.
>
> Great!
>
> > 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.***".
>
> 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.
>
> Best regards,
> 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 on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/595323c3-847a-4d16-af90-e893fc91ef56n%40googlegroups.com.

Reply via email to