Hi everyone, I recently adopted docker-java-api-plugin <https://github.com/jenkinsci/docker-java-api-plugin>, which is a wrapper around docker-java, a Docker API Java client <https://github.com/docker-java/docker-java>, used by other plugins like docker-plugin <https://github.com/jenkinsci/docker-plugin>.
I released yesterday a 3.1.5 version, to make the corresponding version of docker-java available and benefit of new features and bug fixes. Unfortunately, the upgrade introduced some breaking changes (ie. moving classes), and it broke dependant plugins for users who installed the docker-java-api-plugin update (see https://github.com/jenkinsci/docker-plugin/issues/782). Of course, the easy workaround is to downgrade docker-java-api-plugin to the previous version. I really don't like breaking things and I was wondering if there were a way to avoid this and still be able to move forward. Dependant plugins are able to declare a minimum version of a dependency, but not a maximum version. Is there any way for me to declare a breaking change in the plugin manifest? Thank you for your help. Cheers, Eric. -- 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/67447bbf-3202-477c-9082-732ee1cd65ad%40googlegroups.com.
