Looking at history of oak-core/pom.xml this change was done in [1] for OAK-1708 most like to support loading of various DB drivers from within Oak Core and probably a temp change which was not looked back again. That might not be required now as the DataSource gets injected and oak-core need not be aware of drivers etc. So we can get rid of that
@Julian - Thoughts? Chetan Mehrotra [1] https://github.com/apache/jackrabbit-oak/commit/7f844d5cde52dc53c41cc01aad9079afb275438a On Mon, Oct 26, 2015 at 4:20 PM, Francesco Mari <[email protected]> wrote: > A friendly reminder of this issue. Is there a specific reason why > every dependency in oak-core has an optional resolution? > > 2015-10-22 15:34 GMT+02:00 Francesco Mari <[email protected]>: >> Hi, >> >> can somebody explain me why oak-core has the "Import-Package" >> directive set to "*;resolution:=optional"? >> >> The effect of this directive is that *every* imported package is >> declared optional in the manifest file. Because of this, the OSGi >> framework will always resolve the oak-core bundle, even if some of its >> requirements are not satisfied. In particular, oak-core must always be >> ready to cope with NoClassDefFoundExceptions. >> >> We should definitely fix this.
