I use IntelliJ and Maven for building bundles, so the bundle manifests are usually created by a maven plugin, which uses bnd. I'd personally like it to keep it that way as managing bundle manifests manually is a rather tedious exercise. Therefore it would be nice, if Osmorc could create a Manifest on the fly using BND before launching the bundle in any container instead of forcing me to manually create and manage one which is throw away as finally my Manifest is created by Maven anyways. One could add some facet setting like "Let Osmorc keep track of your manifest" and "Create physical manifest", the former using BND to create a manifest and the latter controling whether a physical manifest is created in the source folder. That way you would add two things:
1. Extreme convenience to people who build with 100% IntelliJ as their manifest is updated automagically by BND.
2. Allow people to use external build systems to create manifest but still allowing them to fire up a quick test of their bundles without having to run the external build tool.
This can only be done after the starting of OSGI applications and tests is implemented which is planned for version 0.7.0 in bug OSMORC-8 .