/maven-archiver-2.5/src/site/apt/examples/manifest.apt

 ------
 Manifest
 ------
 Dennis Lundberg
 ------
 2008-01-01
 ------

 ~~ Licensed to the Apache Software Foundation (ASF) under one
 ~~ or more contributor license agreements.  See the NOTICE file
 ~~ distributed with this work for additional information
 ~~ regarding copyright ownership.  The ASF licenses this file
 ~~ to you under the Apache License, Version 2.0 (the
 ~~ "License"); you may not use this file except in compliance
 ~~ with the License.  You may obtain a copy of the License at
 ~~
 ~~   http://www.apache.org/licenses/LICENSE-2.0
 ~~
 ~~ Unless required by applicable law or agreed to in writing,
 ~~ software distributed under the License is distributed on an
 ~~ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
 ~~ KIND, either express or implied.  See the License for the
 ~~ specific language governing permissions and limitations
 ~~ under the License.

Manifest

* Default Manifest

 The default manifest created by Maven Archiver will contain the following
 bits of information:

+-----+
Manifest-Version: 1.0
Archiver-Version: Plexus Archiver
Created-By: Apache Maven
Built-By: ${user.name}
Build-Jdk: ${java.version}
+-----+

* Adding Implementation And Specification Details

 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
Archiver-Version: Plexus Archiver
Created-By: Apache Maven
Built-By: ${user.name}
Build-Jdk: ${java.version}
Specification-Title: ${project.name}
Specification-Version: ${project.version}
Specification-Vendor: ${project.organization.name}
Implementation-Title: ${project.name}
Implementation-Version: ${project.version}
Implementation-Vendor-Id: ${project.groupId}
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.

 <<Note:>> If your pom.xml does not have a <<<\<name\>>>> element, then the
 <<<Specification-Title>>> and <<<Implementation-Title>>> entries will have
 "Unnamed - $\{project.groupId\}:$\{project.artifactId\}:$\{project.version\}" as their value.