Re: integrating a JavaScript library in a Sling project that doesn't have a public Java API

2014-10-27 Thread Sandro Boehme
Hello again, sadly it didn't work using the capabilities/requirements model as the OBR doesn't support the require-capability header [1]. But using a fake package it works as expected. [1] -

integrating a JavaScript library in a Sling project that doesn't have a public Java API

2014-10-24 Thread Sandro Boehme
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

Re: integrating a JavaScript library in a Sling project that doesn't have a public Java API

2014-10-24 Thread Felix Meschberger
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

Re: integrating a JavaScript library in a Sling project that doesn't have a public Java API

2014-10-24 Thread Sandro Boehme
Yay that sounds like the right path! Thanks Felix for the hint! I'm looking forward to David Bosschaerts pointers to use the Provide-/Require-Capability model! I am referring to the provider bundle at https://github.com/sandroboehme/jsNodeTypes. Is that correct ? Yes, thats correct. Thanks,

Re: integrating a JavaScript library in a Sling project that doesn't have a public Java API

2014-10-24 Thread Sandro Boehme
Hi David, thanks for your detailed feedback! I will work on the generic capabilities/requirements model first as Felix and you suggested, as it looks like I can use Require-Capability/ and Provide-Capability/ as instructions in the configuration of the maven-bundle-plugin as seen here