Search V2 public API uses unexported package com.atlassian.confluence.search.v2.aggregator, breaking third-party apps

XMLWordPrintable

    • Severity 2 - Major
    • 122

      Issue Summary

      After upgrading to Confluence 10.2.16 or 10.2.17, third-party apps that consume the Search V2 public API, fail to install or start.

      A new package com.atlassian.confluence.search.v2.aggregator was added to the public SearchManager API but was omitted in the exports of public-api.yaml. Because the package is not exported to third parties, OSGi cannot resolve the affected bundle leading to broken apps.

      Steps to Reproduce

      1. Install Confluence 10.2.16
      2. Install / enable a third-party app that imports the Search V2 API (com.atlassian.confluence.search.v2).
      3. Restart Confluence
      4. Observe the app failing to start and the error in the log.

      Expected Results

      The third-party app resolves and starts successfully. Any package exposed through a public API (SearchManager) is exported to third-party plugins via public-api.yaml, so consumers can load the API without OSGi resolution failures.

      Actual Results

      The app fails OSGi resolution because the package com.atlassian.confluence.search.v2.aggregator is used by the public SearchManager API but is not exported to third-party plugins. The below exception is thrown in the atlassian-confluence.log file:

      org.osgi.framework.BundleException: 
      ... Caused by: (Unresolved requirement) com.atlassian.confluence.search.v2.aggregator 
      

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

              Assignee:
              Manonmani Muthukrishnan
              Reporter:
              Ganesh Gautam
              Votes:
              19 Vote for this issue
              Watchers:
              25 Start watching this issue

                Created:
                Updated:
                Resolved: