 <p>I assume that you're using the <a href="http://wso2.com/library/tutorials/develop-osgi-bundles-using-maven-bundle-plugin" rel="nofollow">maven-bundle-plugin</a> to build the bundle. If so, in your extension project pom file, recheck maven-bundle-plugin configurations. </p> <p>Check whether the <code>Bundle-SymbolicName</code> has being provided to the plugin. You may refer to <a href="https://github.com/wso2-extensions/siddhi-window-unique-time/blob/master/pom.xml#L64" rel="nofollow">this example of another extension, being written to Siddhi</a>.</p> <p><a href="https://github.com/wso2/carbon-kernel/blob/v4.4.3/core/org.wso2.carbon.server/src/main/java/org/wso2/carbon/server/extensions/DropinsBundleDeployer.java#L107" rel="nofollow">According to the source code</a> (the source of Carbon 4.4.3 DropinsBundleDeployer which deploys the bundles we put into the dropins folder), this error could occur:</p> <ol> <li>when the <code>Bundle-SymbolicName</code> has not being given or </li> <li>when the <code>Bundle-Version</code> has not being given.</li> </ol> <p>So in case, putting the <code>Bundle-SymbolicName</code> in to the config didn't make a difference, I would try adding the <code>Bundle-Version</code> as well. You can find a sample config in this <a href="http://wso2.com/library/tutorials/develop-osgi-bundles-using-maven-bundle-plugin" rel="nofollow">maven-bundle-plugin tutorial</a>.</p>