the package names are still the same as far as I understand, and this would still have issues due to the nature of the dependencies.
as k8s has dependencies on both -creds and -api if the creds where updated to use the new -6-api when the classess that k8s would see would be a bit "iffy" would they not (as they would see both -6-api and -api) whith some interesting conflicting results.... > i, jackson-databind and jackson2-api, bootstrap4-api and bootstrap5-api . all doing it that way AFAIUI. because the underlying libraries are well behaved and used a new namespace for the new version? (at least the java ones - I do not know about the JS stuff...) On Thursday, January 5, 2023 at 4:55:03 PM UTC db...@cloudbees.com wrote: > On Thu, Jan 5, 2023 at 5:18 PM Vincent Latombe <vincent...@gmail.com> > wrote: > >> A new major version of this library (6.x) has been available for a while >> and has breaking changes (See >> https://github.com/fabric8io/kubernetes-client/blob/v6.3.1/doc/MIGRATION-v6.md >> >> for details) requiring coordinated changes across plugins using this >> library in the Jenkins ecosystem. >> > > Would a new library plugin for the new major release not solve this > problem in a way much less likely to affect existing users? There's already > jquery and jquery3-api, commons-lang-api and commons-lang3-api, > jackson-databind and jackson2-api, bootstrap4-api and bootstrap5-api, etc. > all doing it that way AFAIUI. > -- 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/069e1ea0-31da-4995-90e3-8ca72d9b16ean%40googlegroups.com.
