pom.xml

<?xml version="1.0" encoding="UTF-8"?>
<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>
	<!-- telus.archetype.version:20150306.Application.Complete -->

	<parent>
		<groupId>telus-maven.dependencyManagement</groupId>
		<artifactId>TELUS_Base_Dependencies</artifactId>
		<version>3.0.2</version>
	</parent>

	<groupId>net.telus.webmail</groupId>
	<artifactId>pwm-flush</artifactId>
	<version>1.0.0</version>
	<packaging>pom</packaging>
	<name>pwm-flush</name>
	
	<properties>
      <application.common.version>1.0.0</application.common.version>
	  <application.shared.version>1.0.0</application.shared.version>
	  <application.app-config.version>1.0.0</application.app-config.version>
   </properties>

	<dependencyManagement>
		<!-- Use this section to define additional 3rd party or Application jars that are
			not specified in the telus-maven.dependencyManagement:TELUS_Frameworks6 pom but
			used by the various modules of the application.
			
			This configuration section does not result in a JAR being downloaded or included in the project.
			On the other hand, this allows author to directly specify which version of 
			a dependency should be used for transitive dependencies or dependencies where 
			version number has not been specified. This is a simple way to force Maven 
			to select a specific dependency version. In the case of an aggregate project, 
			it is best to add this to the aggregate pom since it specifies the dependency versions 
			in one place for all of the child modules. -->		
		<dependencies>

		</dependencies>
	</dependencyManagement>
</project>