Thanks Peter,

you were absolutely right. It was just another package called "controllers". I dind't think of that. I thought it was looking for some kind of capability or so, because a package named just "controllers" is quite unusual. Now I can continue to fight through the dependencies ;)

So, since JPM is gone, is there an easy way to setup a Maven repository in bndtools? Of course there is the article on[1], but it's very brief and I never understood, what exactly has to be done to get this working.


Am 27.04.2017 um 18:51 schrieb Peter Kriens:
It seems that it is looking for a package called ‘controllers’ and can’t find 
anyone exporting it.

Bndtools has a ‘Resolution view’. Select the JAR in the Repository view and it 
should give you the information of its requirements and capabilities. You can 
also search for packages in Bndtools, click on the flashlight in the repository 

Once there was JPM of course :-( I’ve heard you can also search for packages on 
maven central.

Kind regards,

        Peter Kriens

On 27 Apr 2017, at 12:11, Henrik Niehaus <> wrote:

I'm trying to create a bundle, which contains a library with a lot of 
dependencies. While working through all the missing dependencies, I now got 
this error, which doesn't mean anything to me. Can someone shine some light on 
this? What does this mean and how can I find out, which dependency causes the 

Unable to resolve <<INITIAL>> version=null:
   missing requirement
->  Unable to resolve 
   missing requirement controllers]

I also took a screenshot of the bndtools resolution dialog:

I'm using Eclipse Neon with bndtools 3.3.0.REL-20160922-205148-g069791c



OSGi Developer Mail List
OSGi Developer Mail List

OSGi Developer Mail List

Reply via email to