Thanks for the answers, I think I have a workaround (I wouldn't call it a solution though).

@earcar is on the right track, although that solution doesn't leverage all of the information available in the pom.xml that is available in the 3rd party bundle already (particularly the dependencies).

So what seems to work, even though the documentation for the deploy:deploy-file is a little vague, is that you can pass a pom.xml file AND also set the packaging parameter at the same time. So my command line now looks like this:

mvn deploy:deploy-file -Dfile=3rdpartybundle.jar -DpomFile=pom.xml -DrepositoryId=internal -Durl=http://internalserver/nexus -Dpackaging=jar


Doing it this way, the pom.xml in the repository still says that the packaging is of type "bundle", and includes all of the dependencies etc., but the artifact itself has a .jar file extension.

Then when we declare our dependency as type JAR, Maven is able to resolve it successfully:

    &lt;dependency&gt;
        &lt;groupId&gt;...&lt;/groupId&gt;
        &lt;artifactId&gt;...&lt;/artifactId&gt;
        &lt;version&gt;...&lt;/version&gt;
        &lt;type&gt;jar&lt;/type&gt;
    &lt;/dependency&gt;


This basically solves our problem. I am not sure how portable or reliable this is though. FWIW, we are running Maven 3.0.3

Thanks for the help.

How to deploy OSGi bundle to Maven repo with deploy:deploy-file?
I recognized something strange:
On my MacBook Pro (Mid 2008, Mavericks) I get suggestions when searching in the Mac App Store.
But on my MacBook Air (Late 2010, Mavericks) I don't get them.


