|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
The scenario described, can not be handled by a plugin. This only happens if an optional dependency (plugin) gets installed after the origin plugin. Jenkins tells (correctly) the plugin is installed, but the classes of the new plugin are not available in the class loader to the original plugin.
If possible, then this can only be fixed in the core.