<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
	<modelVersion>4.0.0</modelVersion>
	<groupId>fr.neatmonster</groupId>
	<artifactId>nocheatplus-parent</artifactId>
	<packaging>pom</packaging>
	<version>1.1-SNAPSHOT</version>
	<name>NoCheatPlus Parent</name>
	<url>https://dev.bukkit.org/projects/nocheatplus</url>
	<properties>
		<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
		<maven.build.timestamp.format>yyyy_MM_dd-HH_mm</maven.build.timestamp.format>
		<buildTimestamp>${maven.build.timestamp}</buildTimestamp>
		<BUILD_NUMBER>?</BUILD_NUMBER>
		<BUILD_SERIES>?</BUILD_SERIES>
	</properties>

	<!-- Default modules. -->
	<modules>
		<module>NCPBuildBase</module>
		<module>NCPCommons</module>
		<module>NCPCore</module>
		<module>NCPCompatBukkit</module>
		<module>NCPCompatProtocolLib</module>
		<module>NCPPlugin</module>
		<module>NoCheatPlus</module>
	</modules>

	<!-- Profiles for enabling/disabling features. -->
	<profiles>
		<profile>
			<id>nonfree_build</id>
			<modules>
				<module>NCPCompatNonFree</module>
				<module>NCPCompatNonFreeJar</module>
			</modules>
		</profile>
	</profiles>

	<repositories>
		<repository>
			<id>spigot-repo</id>
			<url>https://hub.spigotmc.org/nexus/content/repositories/snapshots</url>
		</repository>
		<!-- <repository> <id>md_5-releases</id> <url>http://repo.md-5.net/content/repositories/releases/</url> 
			</repository> <repository> <id>md_5-snapshots</id> <url>http://repo.md-5.net/content/repositories/snapshots/</url> 
			</repository> -->
		<repository>
			<id>bukkit</id>
			<url>http://repo.bukkit.org/content/groups/public/</url>
		</repository>
	</repositories>

	<description>The initial pom design had been taken from mbax (GitHub).

The naming of the native compatibility modules mostly follows NCPCompat + shortcut of server mod name + earliest build/version that the module would run with (though it should be compiled with the latest available build rather, latest build also can be used, if it is the first module depicting an API incompatibility transition).

NCPCompatBukkit provides compatibility for the Bukkit-API only (no native module available), aiming at keeping NCP up for a new MC version for if no native module is available . Tendency is to use the latest Bukkit version rather, but since it is used for some &quot;unknown mods&quot; as well, it is not compiled with the latest Bukkit version always.

TODO: Better place for descriptions like this?</description>

	<build>
		<plugins>
			<plugin>
				<groupId>org.apache.maven.plugins</groupId>
				<artifactId>maven-deploy-plugin</artifactId>
				<configuration>
					<skip>true</skip>
				</configuration>
			</plugin>
			<plugin>
				<groupId>org.apache.maven.plugins</groupId>
				<artifactId>maven-compiler-plugin</artifactId>
				<version>2.5.1</version>
				<configuration>
					<source>1.6</source>
					<target>1.6</target>
				</configuration>
			</plugin>
		</plugins>
	</build>

</project>
