Adding classes to OSGi boot class loader (BootDelegation)

Still need help?

The Atlassian Community is here for you.

Ask the community

Platform notice: Server and Data Center only. This article only applies to Atlassian products on the server and data center platforms.

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.*

DescriptionAppending third-party classes to OSGi's (plugin framework) boot loader.
ProductJira, Jira Core, Jira Service Management, Jira Software

Last modified on Jul 5, 2022

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.