src/site/apt/examples/customize-file-name-mapping.apt.vm

  ------
  Customizing The File Name Mapping
  ------
  Stephane Nicoll
  <snicoll@apache.org>
  ------
  2006-11-19

~~ Copyright 2006 The Apache Software Foundation.
~~
~~ Licensed 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.

~~ NOTE: For help with the syntax of this file, see:
~~ http://maven.apache.org/doxia/references/apt-format.html


Customizing The File Name Mapping

  It might happen that your project has the same artifactId for different groups. To avoid file name
  clashing, specify the <<<full>>> file name mapping.

+--------
  <build>
    <plugins>
      <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-ear-plugin</artifactId>
        <version>${project.version}</version>
        <configuration>
           [...]
           <fileNameMapping>full</fileNameMapping>
        </configuration>
      </plugin>
    </plugins>
  </build>
+---------

  As a result, each artifact file name will be prefixed by the groupId to avoid clashes. There is also a
  <<<no-version>>> file name mapping if you do not want to get the version in the file names.