Every time I get in and turn the key nothing happens. After turning the key a number of times, it will start up as normal. I have had a new battery, and new wiring to the starter motor installed, and also gotten a new key. Still the same thing is happening. My car is a 2006 Kia Sedona diesel.


Question: How to deploy OSGi bundle to Maven repo with deploy:deploy-file?
Answer: The issue is that "3rdpartybundle.jar" is being built without setting extensions=true and/or supported types:

&lt;plugin&gt;
    &lt;groupId&gt;org.apache.felix&lt;/groupId&gt;
    &lt;artifactId&gt;maven-bundle-plugin&lt;/artifactId&gt;
...
    &lt;extensions&gt;true&lt;/extensions&gt;
...
    &lt;configuration&gt;
        &lt;supportedProjectTypes&gt;
            &lt;supportedProjectType&gt;jar&lt;/supportedProjectType&gt;
            &lt;supportedProjectType&gt;war&lt;/supportedProjectType&gt;
        &lt;/supportedProjectTypes&gt;


If you can't fix that upstream, then there's a couple of options;

1) Repack it as a Jar using a new project pom:

                    &lt;plugin&gt;
                            &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt;
                            &lt;artifactId&gt;maven-dependency-plugin&lt;/artifactId&gt;
                            &lt;version&gt;2.3&lt;/version&gt;
                            &lt;configuration&gt;
                                    &lt;actTransitively&gt;false&lt;/actTransitively&gt;
                                    &lt;outputDirectory&gt;target/classes&lt;/outputDirectory&gt;
                                    &lt;artifactItems&gt;
                                            &lt;artifactItem&gt;
                                                    &lt;groupId&gt;3rd&lt;/groupId&gt;
                                                    &lt;artifactId&gt;party&lt;/artifactId&gt;
                                                    &lt;version&gt;X.Y.Z&lt;/version&gt;
                                            &lt;/artifactItem&gt;
                                    &lt;/artifactItems&gt;
                            &lt;/configuration&gt;
                            &lt;executions&gt;
                                    &lt;execution&gt;
                                            &lt;goals&gt;
                                                    &lt;goal&gt;unpack&lt;/goal&gt;
                                            &lt;/goals&gt;
                                            &lt;phase&gt;compile&lt;/phase&gt;
                                    &lt;/execution&gt;
                            &lt;/executions&gt;
                    &lt;/plugin&gt;


2) Try using  mvn deploy:deploy-file with -DgeneratePom=false -Dpackaging=jar -Dfile=/path/to/3rdpartybundle.jar but without specifying -DpomFile= - hope there's no META-INF/maven/pom.xml inside the 3rdpartybundle.jar - it should work using this but you'll need to specify the groupId/artifactId/version parameters as these won't be derived from the project's pom.

I know I've build bundle artifacts in the past and deployed these to our nexus (v1.9.0.1) and those in the Spring repo are typed bundle too, but don't recall any issue. (Incidentally you don't need to specify the bundle in dependency declarations, AFAIK if it's the only artifact it should be inferred)