pom.xml

<?xml version="1.0"?>
<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/maven-v4_0_0.xsd">
	<modelVersion>4.0.0</modelVersion>
	<groupId>org.openolat</groupId>
	<artifactId>openolat-lms</artifactId>
	<version>7.1.2.0-SNAPSHOT</version>
	<packaging>war</packaging>
	<name>OpenOLAT LMS</name>
	<url>http://www.openolat.org</url>
	<description>
  Welcome to the OpenOLAT (Open Online Learning And Training) Developer Project Site.  This site
  contains materials chiefly of concern to developers (e.g., unit testing and SCA output etc.)
  and is rebuilt periodically on a regular basis.  The site structure is divided between
  project information (e.g., infrastructure, mailing lists, repositories etc.) and reports
  (e.g., unit testing, SCAs etc.)
  </description>
	<organization>
		<name>OpenOLAT</name>
		<url>http://www.openolat.org/</url>
	</organization>
	<licenses>
		<license>
			<name>Apache 2.0 Open Source License</name>
			<url>http://www.apache.org/licenses/LICENSE-2.0</url>
			<distribution>manual</distribution>
			<comments>
		OpenOLAT 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.
		</comments>
		</license>
	</licenses>
	<distributionManagement>
		<repository>
			<id>releases</id>
			<name>OpenOLAT Internal Nexus Release Repository</name>
			<url>http://nexus.openolat.org/nexus/content/repositories/releases</url>
		</repository>
		<snapshotRepository>
			<id>snapshots</id>
			<name>OpenOLAT Internal Nexus Snapshot Repository</name>
			<url>http://nexus.openolat.uzh.ch/nexus/content/repositories/snapshots</url>
		</snapshotRepository>
	</distributionManagement>
	<issueManagement>
		<system>JIRA</system>
		<url>http://jira.openolat.org</url>
	</issueManagement>
	<scm>
		<connection>scm:hg:http://hg.openolat.org</connection>
		<developerConnection>scm:hg:http://hg.openolat.org</developerConnection>
		<url>http://hg.openolat.org</url>
	</scm>
	<mailingLists>
		<mailingList>
			<name>openolat</name>
			<subscribe>https://groups.google.com/forum/#!forum/openolat</subscribe>
			<post>openolat@googlegroups.com</post>
			<archive>https://groups.google.com/forum/#!forum/openolat</archive>
		</mailingList>
	</mailingLists>
	<!-- Unless otherwise explicitly stated the character encoding for all resources 
		(e.g., source, test etc.) will be UTF-8. This can be overriden at the plugin 
		level if necessary. -->
	<properties>
		<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
		<org.springframework.version>3.0.5.RELEASE</org.springframework.version>

    <!-- properties for testing and Q&A -->
    <!-- by default no tests are executed so far (April 2011). Use appropriate profiles and properties on the command line -->
    <skipTests>true</skipTests>
    <skipITs>true</skipITs>
    <!-- properties to define the testing environment
          values: hsql / mysql -->
    <test.env>hsql</test.env>
    <!-- olat.local.properties to distinguish multiple single and cluster olat instances on a single machine-->
    <test.env.db.name>olattest</test.env.db.name>
    <test.env.db.user>olat</test.env.db.user>
    <test.env.db.pass>olat</test.env.db.pass>
    <test.env.db.host.port>3306</test.env.db.host.port>
    <test.env.db.postgresql.user>postgres</test.env.db.postgresql.user>
    <test.env.db.postgresql.pass>postgres</test.env.db.postgresql.pass>
    <test.env.db.postgresql.host.port>5432</test.env.db.postgresql.host.port>
    <test.env.db.hibernate.ddl.auto>create</test.env.db.hibernate.ddl.auto>
    <test.env.instance.id>myolat</test.env.instance.id>
    <test.env.jms.broker.port>61616</test.env.jms.broker.port>
    <test.env.jmx.rmi.port.0>3000</test.env.jmx.rmi.port.0>
    <test.env.jmx.rmi.port.1>3001</test.env.jmx.rmi.port.1>
    <test.env.jmx.rmi.port.2>3002</test.env.jmx.rmi.port.2>

    <!-- this version is defined by the dependency <groupId>org.olat.testutils</groupId>   <artifactId>zipped-tomcat6x</artifactId> and the herein zipped tomcat installation -->
    <container.tomcat.version>6.0.32</container.tomcat.version>
    <!-- install dir is important for the -Pinstall-tomcats profile.
         These few lines define the default tomcat installation variables for installation and running a local tomcat cluster.
         If you want to reuse an existing tomcat installation, set the container.tomcat.*.home instead. -->
    <container.tomcat.one.install.dir>${basedir}/cargo/tomcat/one/</container.tomcat.one.install.dir>
    <container.tomcat.one.home>${container.tomcat.one.install.dir}/apache-tomcat-${container.tomcat.version}</container.tomcat.one.home>
    <!-- The port.part is used in several places to create cluster which follows the template:
         servlet port 8181
         administration ports 8109, 8105
         go to the src/test/profile/cluster/tomcat*/conf and lib/ to see the actual replacements.-->
    <container.tomcat.one.port.part>81</container.tomcat.one.port.part>
    <container.tomcat.one.port>${container.tomcat.one.port.part}${container.tomcat.one.port.part}</container.tomcat.one.port>
    <container.tomcat.two.install.dir>${basedir}/cargo/tomcat/two/</container.tomcat.two.install.dir>
    <container.tomcat.two.home>${container.tomcat.two.install.dir}/apache-tomcat-${container.tomcat.version}</container.tomcat.two.home>
    <container.tomcat.two.port.part>82</container.tomcat.two.port.part>
    <container.tomcat.two.port>${container.tomcat.two.port.part}${container.tomcat.two.port.part}</container.tomcat.two.port>

    <!-- the selenium client version which is also by the maven-selenium-plugin, 
        using the latest selenium a.k.a selenium 2.0 needs a migration of the tests and maven setup. -->
    <selenium-client.version>1.0.2</selenium-client.version>
    <!-- the selenium configuration needed to configure the tomcats, selenium context and maven failsafe (testng) runner.
         The tomcat knows which user to add just for selenium testcases, see additionalUserContext.xml
         The selenium context is defined in the defaultcontext.xml and has variable replacements as specified above.
         The failsafe plugin uses the testng.xml file which comes from this folder.
         In order to customize the selenium tests execution follow the steps:
         1) copy the test/profile/selenium/config folder to a save place
         2) edit the contents of the files (i.e. change executed seleniumtests, add firefox browser executable path to defaultcontext.xml etc.)
         3) run maven among other parameters with -Dselenium.config.files.path="<your-path-without-special-chars>" -->
    <selenium.config.files.path>src/test/profile/selenium/config</selenium.config.files.path>
    <!-- proposal for setting the firefox executable path, which could be used as variable in the defaultcontext.xml
         important if using a firefox script which does not allow to kill the firefoxes after usage. (e.g. Suse 64Bit)-->
    <selenium.config.firefox.path>unused/by/default</selenium.config.firefox.path>

    <!-- properties for debugging -->
    <!-- for debugging reason it may be helpful to set this with 
    -Dcargo.container.wait=true to see if the container is up and running for the seleniumtests. -->
    <cargo.container.wait>false</cargo.container.wait>
    <cargo.container.timeout>300000</cargo.container.timeout>
	</properties>
	<profiles>
		<profile>
		<!-- this serves as an example of how to run something whenever the os familiy matches unix (includes linux as well) -->
			<id>linux</id>
			<activation><os><family>unix</family></os></activation>
			<properties>
				<os.property.file>linux.properties</os.property.file>
			</properties>
			
		</profile>
		<profile>
		<!-- this serves as an example of how to run something whenever the os familiy matches unix (includes linux as well) -->
			<id>windows</id>
			<activation><os><family>windows</family></os></activation>
			<properties>
				<os.property.file>win.properties</os.property.file>
			</properties>
		</profile>

		<profile>
			<id>documentation</id>
			<build>
				<plugins>
					<plugin>
						<groupId>com.sun.tools.jxc.maven2</groupId>
						<artifactId>maven-jaxb-schemagen-plugin</artifactId>
					</plugin>
					<plugin>
						<groupId>org.apache.maven.plugins</groupId>
						<artifactId>maven-javadoc-plugin</artifactId>
					</plugin>
					<plugin>
						<groupId>com.sun.jersey.contribs</groupId>
						<artifactId>maven-wadl-plugin</artifactId>
					</plugin>
					<plugin>
						<groupId>org.codehaus.mojo</groupId>
						<artifactId>xml-maven-plugin</artifactId>
					</plugin>
				</plugins>
			</build>
		</profile>
		

    <profile>
      <id>hsqlunittests</id>
      <activation>
        <property>
          <name>with-hsql</name>
        </property>
      </activation>
      <properties>
        <skipTests>false</skipTests>
        <skipITs>true</skipITs>
        <testFailureIgnore>false</testFailureIgnore>
        <test.env.db.hibernate.ddl.auto>create</test.env.db.hibernate.ddl.auto>
        <test.env>hsql</test.env>
      </properties>
      <build>
        <plugins>
          <plugin>
            <!-- Documentation: http://maven.apache.org/plugins/maven-surefire-plugin/ -->
            <groupId>org.apache.maven.plugins</groupId>
            <artifactId>maven-surefire-plugin</artifactId>
            <version>2.8.1</version>
            <configuration>
              <argLine>-XX:MaxPermSize=256m -Xmx1024m -Xms256m</argLine>
            	<systemPropertyVariables>
								<java.io.tmpdir>${project.build.directory}/olatdata</java.io.tmpdir>
							</systemPropertyVariables>
              <testNGArtifactName>none:none</testNGArtifactName>