From Neil Bartlett:

---%<---
You might want to take a look at bndtools.launcher, here on GitHub:
https://github.com/njbartlett/bndtools.launcher

This is a runtime component that is independent of bndtools and
Eclipse, and it's how I run an OSGi Framework from within bndtools.
Everything is driven by a simple properties file, and it can launch
any OSGi R4.2 compliant framework in a standard way (i.e. without
using any Equinox or Felix specific code).

A really cool feature is that the launcher occasionally checks whether
the properties file has been changed, or whether any of the runtime
bundles have changed. If they have then it either updates or
installs/uninstalls bundles on the fly. So in bndtools, as soon as you
save a Java source file, the bundle is rebuilt and then redeployed
into the runtime. (Of course you can also turn this feature OFF if you
don't want it!)

Documentation is here: http://njbartlett.name/bndtools-runtime#BndtoolsLauncher

To make this work with Maven I think you would just have to map the
logical bundle names from the Maven repository and/or workspace into
full absolute paths.
---%<---