Thank you for this input Jesse. So if I went down this road, I guess at least @DataBoundSetter and @DataBoundConstructor would have to be kept for pipeline scripts. What about the getters? Do they hold the same value? Are getters (can be ?) used by pipeline scripts? (Sorry for asking so many questions, I don't know all possible use cases of a Jenkins plugin :) )
Le lundi 3 janvier 2022 à 21:33:03 UTC+1, Jesse Glick a écrit : > On Fri, Dec 31, 2021 at 8:14 AM 'Réda Housni Alaoui' via Jenkins > Developers <jenkin...@googlegroups.com> wrote: > >> Looking at https://plugins.jenkins.io/sonar-gerrit/#dependencies, I do >> not see any public dependent plugin. >> What's the policy in this kind of situation? >> >> Should I go ahead and potentially break compatibility with private >> dependent plugins? >> > > I would not waste time trying to preserve compatibility with a > hypothetical dependent plugin, unless you have some particular reason to > believe that such a plugin might exist. Anyone wishing to have their usages > taken into consideration ought to be publishing their own plugin on the > Jenkins update center and hosting on @jenkinsci. We routinely remove > unwanted APIs from Jenkins core and API-oriented plugins that appear to > have no usage in the known ecosystem. Occasionally a documented public > method will really have a known usage solely in a private plugin, but this > is pretty uncommon, and I would not expect a miscellaneous Java setter in > an end-user plugin to be used like that. > -- 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/6758db53-044d-4e39-ab54-60e5a488a9abn%40googlegroups.com.
