On Tue, Mar 15, 2022 at 11:00 AM 'Cyrille Le Clerc' via Jenkins Developers <jenkinsci-dev@googlegroups.com> 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 Jenkins project's Artifactory server. This is the path of least resistance, as it allows us to reuse existing infrastructure. Projects that are only consumed by the Jenkins community will have no issue with this. Projects that are consumed outside of the Jenkins community need to adjust their build to add the Jenkins project's Artifactory server. I think this is a reasonable burden to bear in exchange for the infrastructure provided by the Jenkins project, but if somebody feels strongly otherwise they can always set up releases to e.g. Maven Central. My plan for syslog-java-client was to follow the existing pattern and publish new releases exclusively to the Jenkins project's Artifactory server. -- 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/CAFwNDjoQCcztjYn1SLU8Sha55_1EDCD1VCDuj0wuiUwHAp403A%40mail.gmail.com.
