STS, Spring DM, bundler and empty MF

I am using the drag-and-drop functionality in STS to take an OSGi bundle and deploy it into Spring DM. My problem is that while the drag-and-drop works, I am using the bundler plugin in an attempt of trying to have it generate the manifest file dynamically and am ending up with an empty manifest file on the Spring DM server.

Can someone please point out the silly thing I'm doing wrong?

Here are my pom settings:

Code:

---

<plugin>
            <groupId>com.springsource.bundlor</groupId>
            <artifactId>com.springsource.bundlor.maven</artifactId>
            <version>1.0.0.RELEASE</version>
            <configuration>
                <outputManifest>${basedir}/META-INF/MANIFEST.MF</outputManifest>
                <failOnWarnings>false</failOnWarnings>
                <removeNullHeaders>true</removeNullHeaders>
            </configuration>
            <executions>
                <execution>
                    <id>bundlor</id>
                    <goals>
                        <goal>bundlor</goal>
                    </goals>
                    <phase>process-classes</phase>
                </execution>
            </executions>
        </plugin>
                <plugin>
                        <groupId>org.apache.maven.plugins</groupId>
                        <artifactId>maven-jar-plugin</artifactId>
                        <configuration>
                                <archive>
                                        <manifestFile>WebRoot/META-INF/MANIFEST.MF</manifestFile>
                                </archive>
                        </configuration>
                </plugin>
       
         
                  <plugin>
                  <artifactId>maven-war-plugin</artifactId>
                  <configuration>
                    <archive>
                      <manifestFile>${project.build.outputDirectory}/META-INF/MANIFEST.MF</manifestFile>
                    </archive>
                  </configuration>
                </plugin>

---

I did get around the plugin problem by removing it and using the STS Spring Tools generation of the manifest file. This seems to be working after some template.mf tweaking.