I just upgraded our parent-pom from bundlor 1.0.0.M6 to 1.0.0.RELEASE using the following config.
Code:
<plugin>
<groupId>com.springsource.bundlor</groupId>
<artifactId>com.springsource.bundlor.maven</artifactId>
<version>1.0.0.RELEASE</version>
<configuration>
<failOnWarnings>false</failOnWarnings>
<removeNullHeaders>true</removeNullHeaders>
<manifestTemplatePath>template.mf</manifestTemplatePath>
<outputPath>src/main/resources/</outputPath>
</configuration>
<!-- generate the manifest automatically during packaging -->
<executions>
<execution>
<id>bundlor</id>
<goals>
<goal>bundlor</goal>
</goals>
</execution>
</executions>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-jar-plugin</artifactId>
<configuration>
<archive>
<manifestFile>src/main/resources/META-INF/MANIFEST.MF</manifestFile>
</archive>
</configuration>
</plugin>
We're using a pom-first approach where properties are defined in the pom.xml and reused in template.mf. This template.mf is then used by maven to generate a MANIFEST.MF which shall be used inside STS (for deployment into dm server) and be put into the jar (for which we now use the maven-jar-plugin)
cheers
Alex