IOI ioi

Internal Oak Import

Background background

IOI Identifies customer use of internal Oak packages, importing them via OSGi. They are exported without any particular version. Oak bundles or low-level AEM services consume them only.
Some of these areas are used by com.adobe.granite.repository, which sets up a repository for AEM during startup. Another example is the com.adobe.granite.maintenance.oak Adobe bundle, which wraps and provides Oak maintenance tasks.

Possible implications and risks implications-and-risks

  • In a future AEM version internal exports might be removed, causing broken dependencies and inactive bundles depending directly on Oak.
  • API in internal exports might change.

Possible solutions solutions

  • Use the Sling Resource API (or the JCR API) instead of low-level access.
  • Avoid depending on internal packages that are not part of any public API or SPI.
  • Contact the AEM Support Team for clarifications or to have concerns addressed.
recommendation-more-help
c50d24a5-718e-4110-a484-b335e8a63206