We upgrade JIRA to 4.3 and FeCru 2.5 for Studio 2.5. Both products will bundle the UPM. The UPM Permission Service created for AOD-3113 should be moved out of studio-theme-confluence-plugin in order to be reusable. It shouldn't reside in studio-common-components-plugin since Bamboo doesn't provide the UPM yet, imo it would be better to have a separate bundle for it.

The logic for the service resides in com.atlassian.studio.confluence.upm, and is glued together by two Spring context definitions called upm-permission-service-prod.xml and upm-permission-service-unit.xml. The Confluence home discovery (upm-permission-service-prod.xml) and configuration of user-installed plugins (user-installed-plugins.properties) have to stay external to that common plugin.

This could be either achieved by attaching a fragment bundle or consuming the com.atlassian.studio.confluence.upm.PermissionFilter from the OSGi container and split the configuration into another bundle of common filters and product-specific filters (which could remain in the studio-theme-<product>-plugin).