To be honest: Right now I wouldn't care about how mature/immature a project is. Sigil is right now the tool that is closest to the actual philosophy of OSGi. But Sigil doesn't work with Maven (and its way of building stuff is very different from what maven does) OSGi is not only a good platform to build software on but also a modularization framework that helps java to get almost apt-get like functionality. Tools like BND and Bundlor approach the Maven-OSGi-integration from the wrong side. There OSGi is just another app framework with certain build requirements instead of a full module layer that can help dealing with the java dependency hell.
When building an OSGi project I want to a) resolve dependencies exclusively from OBR, thereby avoiding the necessity to check if I really got an OSGi-Bundle and also to resolve transitive dependencies b) specify import/export information once (could be BND, but I want to reuse this information for a) ) CU Jochen
