On Mon, Dec 1, 2014 at 8:11 PM, Jesse Glick <[email protected]> wrote: > This is a core bug; it should [not] have tried to dynamically load a new > plugin with a dependency on another plugin that is only _scheduled_ to > be installed.
In case it was not clear, the workaround is simply to restart Jenkins after plugin installation, not try to use the new plugins in the same session. -- 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/CANfRfr108hSSxV%3D0LYt%3DHtZ1GzRRvRzYtRAToNmhvpuhcWn0Hg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
