Roy Teeuwen created OAK-10222:
---------------------------------
Summary: Provide package dependency on jars / bundles in an OSGi
environment
Key: OAK-10222
URL: https://issues.apache.org/jira/browse/OAK-10222
Project: Jackrabbit Oak
Issue Type: Improvement
Reporter: Roy Teeuwen
We want to be able to state that a package should not install unless a OSGi
bundle is available. There are situations where the package depends on code to
be available before it can be correctly installed.
An example when this is useful is when using an external install hook, which is
not available yet. This could be the case if you have the following content
package:
* {{all (content-package)}}
** {{vendor-framework-all (content-package)}}
*** {{vendor-framework-core (bundle containing hook)}}
** {{application-content (content-package with install hook depending on
vendor-framework-core bundle)}}
An option to be able to fix this in an "easy" approach would for example be by
registering OSGi bundles as packages to the package manager, the bundle
symbolic name and version can be used as package name + version.
Any other suggestions are welcome. I have already tried using an approach from
Sling:
https://sling.apache.org/documentation/bundles/installer-provider-installhook.html.
But this is not possible to use this because you can't put an installPathRegex
from the {{application-content}} content-package on an embedded
{{vendor-framework-core}} package. It also feels like an even bigger hack /
workaround than the proposal
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
