Hi I am a bit confused, sorry.
I am referring to the provider bundle at https://github.com/sandroboehme/jsNodeTypes. Is that correct ? Also having SLING-4001 in mind, I might come to the core of the problem: You want to deploy an application which depends on the functionality of the jsNodeTypes bundle. So you need a way to indicate to OBR that if you application bundle is deployed, the jsNodeTypes bundle must be installed as well. Correct, Require-Bundle used to be the only solution here, though cranky but feasible. Nowadays we do have a more flexible Provide-/Require-Capability model: The jsNodeTypes would Provide-Capability — the jsNodeTypes feature — and your application would Require-Capability this jsNodeTypes feature. I have copied David Bosschaert who can certainly share how this mechanism could be leveraged in this use case. Whether an existing capability can be reused or whether you might want to define a custom capability. Regards Felix [1] https://issues.apache.org/jira/browse/SLING-4001 > Am 24.10.2014 um 11:44 schrieb Sandro Boehme <[email protected]>: > > Hello, > > in the Sling Resource-Editor I would like to integrate the JavaScript > JSNodeTypes library that doesn't have a public Java API. But the user should > still be able to use OSGi to easily install the tool. > > The problem is, when using the maven-bundle-plugin the Bnd tool won't > automatically find the dependency to that library when looking for Java > import statements and I cannot manually add a 'Import-Package' statement as > there is no package I can use. > > There is one thing to note: The JSNodeTypes library is created by myself. > This means if there is a solution that needs changes in that library I could > do that. E.g. I could create an empty Java package in JSNodeTypes that I can > use in an 'Import-Package' statement. > > But isn't there a better solution? > > Thanks, > > Sandro
