The default manifest created by Maven Archiver will contain the following bits of information:
Manifest-Version: 1.0 Created-By: Apache Maven ${maven.version} Build-Jdk: ${java.version}
Note: The Build-Jdk does not take toolchains configuration into account. It is the same JDK version as running the Maven instance.
Starting with version 2.1, Maven Archiver no longer creates the Implementation and Specification details in the manifest by default. If you want them in your manifest you have to say so explicitly in your configuration.
Note: Because this is a recent change in Maven Archiver, different plugins may or may not have started using it yet. Please check the documentation for the plugin you want to use. In this example we use maven-jar-plugin 2.1 which was the first version of that plugin to use this new feature.
<project> ... <build> <plugins> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-jar-plugin</artifactId> <version>2.1</version> ... <configuration> <archive> <manifest> <addDefaultImplementationEntries>true</addDefaultImplementationEntries> <addDefaultSpecificationEntries>true</addDefaultSpecificationEntries> </manifest> </archive> </configuration> ... </plugin> </plugins> </build> ... </project>
The resulting manifest would contain these pieces of information:
Manifest-Version: 1.0 Created-By: Apache Maven ${maven.version} Build-Jdk: ${java.version} Specification-Title: ${project.name} Specification-Version: ${project.artifact.selectedVersion.majorVersion}.${project.artifact.selectedVersion.minorVersion} Specification-Vendor: ${project.organization.name} Implementation-Title: ${project.name} Implementation-Version: ${project.version} Implementation-Vendor: ${project.organization.name}
Note: If your pom.xml does not have an <organization>/<name> element, then the Specification-Vendor and Implementation-Vendor entries will not be in the manifest.