<groupId>org.apache.maven.its.mng3877</groupId>
  <artifactId>test</artifactId>
  <version>1.0</version>
  <packaging>jar</packaging>

  <name>Maven Integration Test :: MNG-3877</name>
  <description>
    Verify that paths to project directories use the platform-specific file separator.
  </description>

  <build>
    <filters>
      <filter>src/main/filters/it.properties</filter>
    </filters>
  </build>

							</mapper>
						</data>
						<data>
							<type>files</type>
							<paths>
								<path>${project.build.directory}/fess/WEB-INF/classes/org/codelibs/fess/FessBoot.class</path>
								<path>${project.build.directory}/fess/WEB-INF/classes/org/codelibs/fess/FessBoot$FessBootPropsTranslator.class</path>
							</paths>
							<dst>${packaging.fess.lib.dir}/classes/org/codelibs/fess/</dst>
							<mapper>

  <!-- profiles
   | This is a list of profiles which can be activated in a variety of ways, and which can modify
   | the build process. Profiles provided in the settings.xml are intended to provide local machine-
   | specific paths and repository locations which allow the build to work in the local environment.
   |
   | For example, if you have an integration testing plugin - like cactus - that needs to know where

    <siteOut>${project.reporting.outputDirectory}</siteOut>
  </properties>

  <build>
    <!--
    NOTE: Deliberately set all build directories to relative paths to ensure they really need basedir alignment.
    -->
    <sourceDirectory>src/main/java</sourceDirectory>
    <testSourceDirectory>src/test/java</testSourceDirectory>

  xsi:schemaLocation="http://maven.apache.org/TOOLCHAINS/1.1.0 http://maven.apache.org/xsd/toolchains-1.1.0.xsd">

  <!--
   | With toolchains you can refer to installations on your system. This
   | way you don't have to hardcode paths in your pom.xml.
   |
   | Every toolchain consist of 3 elements:
   | * type: the type of tool. An often used value is 'jdk'. Toolchains-aware
   |   plugins should document which type you must use.
   |

    <p>With {@code jdk} toolchain, for example, instead of being stuck with the JDK used to run Maven, all plugins can use
    the same other JDK instance without hardcoding absolute paths into the {@code pom.xml}
    and without configuring every plugin that require path to JDK tools.</p>

    @see <a href="/guides/mini/guide-using-toolchains.html">Guide to Using Toolchains</a>
    ]]></description>

  <artifactId>test-parent</artifactId>
  <version>1.0-SNAPSHOT</version>
  <packaging>pom</packaging>

  <name>MNG-3621 :: Parent</name>
  <description>Test inheritance of UNC paths</description>

  <modules>
    <module>child</module>
  </modules>

  <distributionManagement>
    <site>
      <id>site</id>
      <url>file:////host/site</url>
    </site>
  </distributionManagement>