I must admit that the parametrized trigger is not a dependency of my plugin. I've copied it in the plugins folder of my dev environment because it is present in our production environment.
Fearing a similar crash in the production environment, I preferred ask the question to confirmed Java/Jenkins devs. Il giorno mer 25 mar 2015 17:09 Jesse Glick <[email protected]> ha scritto: > On Wed, Mar 25, 2015 at 5:31 AM, Ivo Bellin Salarin > <[email protected]> wrote: > > I suppose this is related to the version of the plugin. > > Perhaps. > > > Is there a way to control the (version of the) class being used? Is this > due to a change in > > the interface of the called class? > > No, you can get such a CCE even if the bytecode is identical. > > I suspect that you are either not declaring your dependency on > promoted-builds and/or parameterized-trigger correctly, or there is > some subtle bug in the way maven-hpi-plugin sets up the test > environment. Normally Maven’s dependency resolution should force one > or the other version to be added to the test classpath (the “closer”, > 2.20 in this case) and that is 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 [email protected]. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/jenkinsci-dev/CANfRfr30R6KFx78HMg64_gba7WMkDdQfUimHAND5n9igoF6gug% > 40mail.gmail.com. > For more options, visit https://groups.google.com/d/optout. > -- 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/CAPc4eF8KCgJOHCW9N%3DxtCHA45Qg-%3DhPyZPjoB%2BuGaf0r6DL7fQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
