Adding classes to OSGi boot class loader (BootDelegation)


アトラシアン コミュニティをご利用ください。


プラットフォームについて: Server および Data Center のみ。この記事は、Server および Data Center プラットフォームのアトラシアン製品にのみ適用されます。

Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Fisheye および Crucible は除く

This problem is related to a third party plugin, and therefore not supported by Atlassian. See Atlassian Supported Plugins for more information.


Some third-party apps or external tools require its classes or dependencies to be loaded by the OSGi framework, and most documented procedures involve modifying the default parameter:

However, this is unsupported and it could cause unintended effects on Jira's startup process or of its installed apps. This is one of the reasons we introduced a new flag to the Atlassian Plugin Framework, our implementation of OSGi:

This new flag will append classes to our default configuration of boot delegation, minimizing the risk of negatively impacting the application's behavior.


To introduce this flag in your installation you may follow the same steps as instructed by the vendor requiring this change to setup their tool or app, but append the '.extra' to the end of the parameter and input only the classes linked to the app or tool. Here is an example:*,com.mycompany.myotherapp.*

説明 Appending third-party classes to OSGi's (plugin framework) boot loader.
製品Jira, Jira Core, Jira Service Management, Jira Software

最終更新日 2022 年 7 月 5 日


Powered by Confluence and Scroll Viewport.