Hi Chris,
the error that you see is because a jar file that does not have an OSGi manifest will get BundleSymbolicName null and version 0.0.0. As soon as you load two of them you get a conflict.
There are several ways to work around that.
The first and easiest is to find versions of your dependencies that have OSGi manifests. Apache, for instance, normally turns most of their libraries into OSGi bundles in case somebody wants to use it that way. If you experience the opposite, it might be because you are using a very old version. For instance, I checked version 1.2 of commons-logging and it has a proper manifest.
Another possibility is to embed dependencies into your bundle rather than having them be loaded as separate entities (or wrap them all up as a single dependency bundle). Depending on which plugin you use in Maven, there might be support for that. The Maven Felix plugin, for instance, can do that: http://felix.apache.org/documentation/subprojects/apache-felix-maven-bundle-plugin-bnd.html#embedding-dependencies
Finally, if your libraries are not OSGi bundles you can also put them into the JVM classpath and let the Concierge system bundle export them by delegating to the classpath. What you need to do to make this happen is putting all relevant packages into -Dorg.osgi.framework.system.packages.extra
Best regards,
Jan.