The documentation for the maven-achiver plugin seems pretty clear that you cannot delete properties, just set them empty, as described in Alex Chernyshev's answer . To get more control over MANIFEST.MF, you should not use the maven-archiver plugin.
One alternative would be to use the maven antrun plugin and the Ant Jar task to create a Jar.
In pom.xml:
<project> ... <build> <plugins> <plugin> <artifactId>maven-antrun-plugin</artifactId> <version>1.7</version> <executions> <execution> <phase>package</phase> <configuration> <target> <jar destfile="test.jar" basedir="."> <include name="build"/> <manifest> <attribute name="Manifest-Version:" value="1.0"/> </manifest> </jar> </target> </configuration> <goals> <goal>run</goal> </goals> </execution> </executions> </plugin> </plugins> </build> ... </project>
Another option is to invoke the Jar tool directly using the Maven exec plugin .
I do not like to recommend antrun, since I consider this a dirty hack, but it seems that the maven-archiver does not meet your requirements. It might be worthwhile to raise a function request for maven-archiver.
EDIT: 2014-10-06 lifted Jira MSHARED-362
EDIT: 2018-06-18: updated link to Jira and Maven Exec plugin
EDIT: 2019-01-14: the fix is ββfor maven-archiver-3.4.0
source share