Re: [Proposal] Transfer of CloudBees-community/syslog-java-client to jenkinsci Github org

Hi all - I'm checking this internally and will come back to you as soon as I have an answer. Thanks On Thursday, March 31, 2022 at 9:25:00 AM UTC+2 cyrille...@elastic.co wrote: > Keeping the same groupId would definitively be the best solution. Let's > see what's CloudBees' answer. > > Cyrille

Re: [Proposal] Transfer of CloudBees-community/syslog-java-client to jenkinsci Github org

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 m...@basilcrow.com wrote: > Hi Cyrille, > > On Wed, Mar 23, 2022 at 3:39 AM 'Cyrille Le Clerc' via Jenkins > Developers wrote: > > I

Re: [Proposal] Transfer of CloudBees-community/syslog-java-client to jenkinsci Github org

Hi Cyrille, On Wed, Mar 23, 2022 at 3:39 AM 'Cyrille Le Clerc' via Jenkins Developers 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

Re: [Proposal] Transfer of CloudBees-community/syslog-java-client to jenkinsci Github org

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

Re: [Proposal] Transfer of CloudBees-community/syslog-java-client to jenkinsci Github org

Cyrille and I both now have access to this repository as members of the syslog-java-client-developers group. I have updated the build to remove any CloudBees-specific parent POMs, run CI builds on Jenkins project

Re: [Proposal] Transfer of CloudBees-community/syslog-java-client to jenkinsci Github org

Is there anyone from CloudBees who wants access to this? On Wed, 16 Mar 2022 at 13:49, 'Cyrille Le Clerc' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote: > > FYI The repository has been transferred: > https://github.com/jenkinsci/syslog-java-client > > Thanks Mikael, > I verified

Re: [Proposal] Transfer of CloudBees-community/syslog-java-client to jenkinsci Github org

> FYI The repository has been transferred: https://github.com/jenkinsci/syslog-java-client Thanks Mikael, I verified the redirection for people who consume the library directly rather than going through a Jenkins plugin and it works like a charm. > My plan for syslog-java-client was to follow

Re: [Proposal] Transfer of CloudBees-community/syslog-java-client to jenkinsci Github org

Thanks all! FYI The repository has been transferred: https://github.com/jenkinsci/syslog-java-client Michaël On Wednesday, March 16, 2022 at 12:13:02 AM UTC+1 m...@basilcrow.com wrote: > On Tue, Mar 15, 2022 at 11:00 AM 'Cyrille Le Clerc' via Jenkins > Developers wrote: > > Did you

Re: [Proposal] Transfer of CloudBees-community/syslog-java-client to jenkinsci Github org

On Tue, Mar 15, 2022 at 11:00 AM 'Cyrille Le Clerc' via Jenkins Developers wrote: > Did you consider publishing exclusively to Jenkins' own maven repository? I have configured the repositories we have transferred already, like Mock JavaMail and File Leak Detector, to publish exclusively to the

Re: [Proposal] Transfer of CloudBees-community/syslog-java-client to jenkinsci Github org

Thanks, I assumed the Jenkins community didn't have the permission to publish on maven central artifacts with the group Id com.cloudbees. Did you consider publishing exclusively to Jenkins' own maven repository? Cyrille Le mar. 15 mars 2022 à 16:29, Basil Crow a écrit : > On Tue, Mar 15, 2022

Re: [Proposal] Transfer of CloudBees-community/syslog-java-client to jenkinsci Github org

On Tue, Mar 15, 2022 at 1:30 AM 'Gavin Mogan' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote: > Why do you need to change the group of? I concur with Gavin. I see no reason to change the Maven group ID or artifact ID, and we have historically not changed these when transferring

Re: [Proposal] Transfer of CloudBees-community/syslog-java-client to jenkinsci Github org

Why do you need to change the group of? If you do a transfer, it'll leave a redirect from the old URL to new url. Plus you can update SCM info in the pom file. If you want to change the group id, I think it should be a fork and leave the old one behind. My 2 cents On Tue., Mar. 15, 2022, 1:27

Re: [Proposal] Transfer of CloudBees-community/syslog-java-client to jenkinsci Github org

A question please: as there are many users of the syslog-java-client outside of the Jenkins community, how do we plan to explain them the migration? I guess we will change the Maven artifact groupID... Can we keep an archived version of the syslog-java-client repo under the CloudBeesCommunity

Re: [Proposal] Transfer of CloudBees-community/syslog-java-client to jenkinsci Github org

Sounds like a perfect plan. Many thanks Cyrille On Monday, March 14, 2022 at 11:26:38 PM UTC+1 m...@basilcrow.com wrote: > On Mon, Mar 14, 2022 at 3:08 PM 'Cyrille Le Clerc' via Jenkins Developers < > jenkin...@googlegroups.com> wrote: > > It's a great idea to allow the syslog-java-client to

Re: [Proposal] Transfer of CloudBees-community/syslog-java-client to jenkinsci Github org

On Mon, Mar 14, 2022 at 3:08 PM 'Cyrille Le Clerc' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote: > It's a great idea to allow the syslog-java-client to progress migrating it to the Jenkins Community. I'm fully supportive. > The MIT License should make it easy. Thank you for the

Re: [Proposal] Transfer of CloudBees-community/syslog-java-client to jenkinsci Github org

It's a great idea to allow the syslog-java-client to progress migrating it to the Jenkins Community. I'm fully supportive. The MIT License should make it easy. Note that I am less involved in Syslog things as I am now focused on OpenTelemetry and particularly at the moment OpenTelemetry Logs as

Re: [Proposal] Transfer of CloudBees-community/syslog-java-client to jenkinsci Github org

+1 from me as well. Once transferred, we will need to add a new YAML file to repository-permissions-updater (RPU) to grant someone GitHub and Artifactory permissions. I am CC'ing Cyrille Le Clerc as the original author and last

Re: [Proposal] Transfer of CloudBees-community/syslog-java-client to jenkinsci Github org

+1 from me On Friday, March 11, 2022 at 3:02:42 PM UTC-7 mpail...@cloudbees.com wrote: > Hi all, > > CloudBees would like to propose a transfer of > CloudBees-community/syslog-java-client > to > the jenkinsci Github organization. >

[Proposal] Transfer of CloudBees-community/syslog-java-client to jenkinsci Github org

Hi all, CloudBees would like to propose a transfer of CloudBees-community/syslog-java-client to the jenkinsci Github organization. This project is currently used by the following projects