Also be aware, that the unique package space that orbit demands breaks any artifact conflict resolution built into the whole maven process. (among other things that maven provides)
Example,
Let say you have a common artifact you are having to orbitize.
You establish groupId: org.eclipse.projectfoo.orbit
You put that artifact into artifactId: javax.ws-rs-api
You now have made extra work for the users of your eclipse project.
All of the users of your project will have to manually exclude either ...
the "org.eclipse.projectfoo.orbit" groupId dependencies if they don't use OSGi, or
the "javax.ws.rx" groupId in multiple other dependencies to use your orbit version for its OSGi-ness.
If the orbit process removes files (which happens, be vigilant of changes to the orbit version!), then your orbit version might be incompatible with other non-osgi libraries that use the same artifact.
If you have growing group of users that use both your orbit dependencies and any build tool that uses the central maven repository system, you'll start to have calls for the -javadoc.jar and -source.jar versions of that orbit dependency as well.
