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.
