EDIT

<?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>

  <groupId>eu.etaxonomy</groupId>

  <artifactId>cdm-server</artifactId>

  <version>5.42.0</version>

  <packaging>jar</packaging>

  <name>CDM Community Standalone Server</name>

  <properties>

    <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>

    <jetty-version>9.4.26.v20200117</jetty-version>

    <doclint>none</doclint>

    <log4j.version>2.19.0</log4j.version>

    <slf4j.version>1.7.36</slf4j.version>

  </properties>

  <scm>

    <!-- see section Provider Configuration in https://maven.apache.org/scm/subversion.html 

      for instructions on how to externalize credentials in $user.home/.scm/svn-settings.xml -->

    <connection>scm:git:https://dev.e-taxonomy.eu/git/cdm-server.git</connection>

    <developerConnection>scm:git:ssh://git@dev.e-taxonomy.eu/var/git/cdm-server.git</developerConnection>

    <url>https://dev.e-taxonomy.eu/gitweb/cdm-server.git/tree</url>

  </scm>

  <prerequisites>

    <maven>3.6.3</maven>

  </prerequisites>

  <mailingLists>

    <mailingList>

      <name>EDIT Platform Developers</name>

      <subscribe>

            https://lists.fu-berlin.de/listinfo/editplatformdevelopers#subscribe

        </subscribe>

      <unsubscribe>

            https://lists.fu-berlin.de/listinfo/editplatformdevelopers#options

        </unsubscribe>

    </mailingList>

    <mailingList>

      <name>EDIT User</name>

      <subscribe>

            https://lists.fu-berlin.de/listinfo/edituser#subscribe

        </subscribe>

      <unsubscribe>

            https://lists.fu-berlin.de/listinfo/edituser#options

        </unsubscribe>

    </mailingList>

  </mailingLists>

  <licenses>

    <license>

      <name>Mozilla Public License Version 1.1</name>

      <url>https://www.mozilla.org/MPL/MPL-1.1.html</url>

      <distribution>repo</distribution>

    </license>

  </licenses>

  <developers>

    <developer>

      <!-- your SVN account id please! -->

      <id>a.kohlbecker</id>

      <name>

        Andreas Kohlbecker

      </name>

      <email>a.kohlbecker [at] bgbm.org</email>

      <organization>

        Botanical Garden Botanical Museum Berlin

      </organization>

      <organizationUrl>https://www.bgbm.org/en/biodiversity-informatics</organizationUrl>

      <timezone>+1</timezone>

      <roles>

        <role>Developer</role>

      </roles>

      <url/>

    </developer>

  </developers>

  <!-- contributors> <contributor> <name>Test-Contributor</name> </contributor> 

    </contributors -->

  <issueManagement>

    <system>Redmine</system>

    <url>https://dev.e-taxonomy.eu/redmine/</url>

  </issueManagement>

  <ciManagement>

    <system>Jenkins</system>

    <url>https://int.e-taxonomy.eu/jenkins</url>

  </ciManagement>

  <!-- **** REPOSITORIES **** -->

  <profiles>

    <profile>

      <id>local-repository</id>

      <activation>

        <property>

          <name>localrepo</name>

        </property>

      </activation>

      <repositories>

        <repository>

          <id>EditLocalRepository</id>

          <url>file://${localrepo}/eu/etaxonomy/</url>

          <releases>

            <enabled>false</enabled>

            <updatePolicy>always</updatePolicy>

          </releases>

          <snapshots>

            <enabled>true</enabled>

            <updatePolicy>always</updatePolicy>

          </snapshots>

        </repository>

      </repositories>

    </profile>

  </profiles>

  <repositories>

    <!-- sun repository -->

    <repository>

      <id>java.net-Public</id>

      <name>Maven Java Net Snapshots and Releases</name>

      <url>https://maven.java.net/content/groups/public/</url>

    </repository>

    <!-- the localhost Maven Repository -->

    <repository>

      <id>EditLocalRepository</id>

      <!-- disable the local repo to let maven always retrieve the latest 

        cdm-webapp.war TODO: use ${localrepo} for ${user.home}/.m2/repository 

        in MAVEN 3 -->

      <url>file://${user.home}/.m2/repository/eu/etaxonomy/</url>

      <releases>

        <enabled>false</enabled>

        <updatePolicy>always</updatePolicy>

      </releases>

      <snapshots>

        <enabled>false</enabled>

        <updatePolicy>always</updatePolicy>

      </snapshots>

    </repository>

    <!-- the EDIT Maven Repository -->

    <repository>

      <id>EditRepository</id>

      <url>https://cybertaxonomy.org/mavenrepo/</url>

      <releases>

        <enabled>true</enabled>

        <updatePolicy>always</updatePolicy>

      </releases>

      <snapshots>

        <enabled>true</enabled>

        <updatePolicy>always</updatePolicy>

      </snapshots>

    </repository>

    <!-- apache incubating repository -->

    <repository>

      <id>ApacheIncubating</id>

      <url>https://people.apache.org/repo/m2-incubating-repository/</url>

    </repository>

  </repositories>

  <!-- **** PLUGINS **** -->

  <build>

    <resources>

      <!-- ${basedir}/src/main/resources -->

      <resource>

        <!-- replace the project-version placeholder in the version.properties 

          file. This property can then be used to retrieve the version number in the 

          Bootloader -->

        <targetPath>${project.build.directory}/classes</targetPath>

        <filtering>true</filtering>

        <directory>${basedir}/src/main/resources</directory>

        <includes>

          <include>version.properties</include>

        </includes>

      </resource>

      <resource>

        <!-- all other files in classes -->

        <targetPath>${project.build.directory}/classes</targetPath>

        <directory>${basedir}/src/main/resources</directory>

        <excludes>

          <exclude>version.properties</exclude>

        </excludes>

      </resource>

      <!-- ${basedir}/src/main/installer/win32 -->

      <resource>

        <targetPath>${project.build.directory}/installer</targetPath>

        <filtering>true</filtering>

        <directory>${basedir}/src/main/installer</directory>

        <includes>

          <include>win32/program-folder/etc/CDMServer.conf</include>

          <include>win32/setup.nsi</include>

        </includes>

      </resource>

      <resource>

        <targetPath>${project.build.directory}/installer</targetPath>

        <directory>${basedir}/src/main/installer</directory>

        <excludes>

          <exclude>win32/program-folder/etc/CDMServer.conf</exclude>

          <exclude>win32/setup.nsi</exclude>

        </excludes>

      </resource>

    </resources>

    <plugins>

      <!-- ====== IDE ====== -->

      <plugin>

        <groupId>org.apache.maven.plugins</groupId>

        <artifactId>maven-eclipse-plugin</artifactId>

        <version>2.10</version>

        <configuration>

          <downloadSources>true</downloadSources>

          <downloadJavadocs>true</downloadJavadocs>

        </configuration>

      </plugin>

      <plugin>

        <!-- only needed for testing the svn credentials credentials are 

          usually stored by svn automatically unless not configured differently in 

          {user.home}\.subversion\config So in order to use a specific svn account 

          with maven firts to a commit manually by svn ci -m "commit message" and answer 

          the question wether to store the credential with yes. There is no specific 

          maven configuration required for svn to work with maven! -->

        <groupId>org.apache.maven.plugins</groupId>

        <artifactId>maven-scm-plugin</artifactId>

        <version>1.9.2</version>

        <configuration>

          <connectionType>developerConnection</connectionType>

        </configuration>

      </plugin>

      <!-- ====== CREATE ====== -->

      <plugin>

        <groupId>org.apache.maven.plugins</groupId>

        <artifactId>maven-resources-plugin</artifactId>

        <!-- creates "compile" error in IDE in maven-dependency-plugin section (see below) since upgrading from 3.1.0 to 3.2.0 -->

        <version>3.2.0</version>

      </plugin>

      <plugin>

        <groupId>org.apache.maven.plugins</groupId>

        <artifactId>maven-compiler-plugin</artifactId>

        <version>3.9.0</version>

        <configuration>

          <source>1.8</source>

          <target>1.8</target>

        </configuration>

      </plugin>

      <plugin>

        <groupId>org.apache.maven.plugins</groupId>

        <artifactId>maven-surefire-plugin</artifactId>

        <version>3.0.0-M7</version>

        <configuration>

          <argLine>-Xmx512M</argLine>

          <includes>

            <include>**/*Test.java</include>

          </includes>

          <systemProperties>

            <property>

              <name>hibernate.connection.driver_class</name>

              <value>${hibernate.connection.driver_class}</value>

            </property>

            <property>

              <name>hibernate.connection.url</name>

              <value>${hibernate.connection.url}</value>

            </property>

            <property>

              <name>hibernate.connection.username</name>

              <value>${hibernate.connection.username}</value>

            </property>

            <property>

              <name>hibernate.connection.password</name>

              <value>${hibernate.connection.password}</value>

            </property>

          </systemProperties>

        </configuration>

      </plugin>

      <!-- ====== CREATE ====== -->

      <plugin>

        <groupId>org.codehaus.mojo</groupId>

        <artifactId>buildnumber-maven-plugin</artifactId>

        <version>1.4</version>

        <executions>

          <execution>

            <!--<phase>deploy</phase> -->

            <goals>

              <goal>create</goal>

            </goals>

          </execution>

        </executions>

        <configuration>

          <doCheck>false</doCheck>

          <!-- Only create the build number if there are no local modifications -->

          <doUpdate>false</doUpdate>

          <!-- automatically update the local svn copy -->

        </configuration>

      </plugin>

      <plugin>

        <groupId>org.apache.maven.plugins</groupId>

        <artifactId>maven-site-plugin</artifactId>

        <version>3.10.0</version>

        <configuration>

          <locales>en</locales>

          <outputEncoding>UTF-8</outputEncoding>

          <chmod>false</chmod>

        </configuration>

      </plugin>

      <!-- ====== VERIFY ====== -->

      <plugin>

        <groupId>org.apache.maven.plugins</groupId>

        <artifactId>maven-source-plugin</artifactId>

        <version>3.2.1</version>

        <executions>

          <execution>

            <id>attach-sources</id>

            <phase>verify</phase>

            <goals>

              <goal>jar</goal>

            </goals>

          </execution>

        </executions>

      </plugin>

      <plugin>

        <groupId>org.apache.maven.plugins</groupId>

        <artifactId>maven-javadoc-plugin</artifactId>

        <version>3.3.1</version>

        <configuration>

          <aggregate>true</aggregate>

          <stylesheet>maven</stylesheet>

          <failOnError>false</failOnError>

          <doclint>${doclint}</doclint>

        </configuration>

      </plugin>

      <!-- ====== PROCESS-SOURCES ====== -->

      <plugin>

        <groupId>org.apache.maven.plugins</groupId>

        <artifactId>maven-dependency-plugin</artifactId>

        <version>3.2.0</version>

        <executions>

          <!-- creates "compile" error in IDE in maven-dependency-plugin section (see below) since upgrading from 3.1.0 to 3.2.0 -->

          <execution>

            <id>copy</id>

            <goals>

              <goal>copy</goal>

            </goals>

            <configuration>

              <silent>flase</silent>

              <stripVersion>true</stripVersion>

              <overWriteSnapshots>true</overWriteSnapshots>

              <overWriteIfNewer>true</overWriteIfNewer>

              <overWriteReleases>true</overWriteReleases>

              <artifactItems>

                <artifactItem>

                  <!-- copy the cdm-webapp-${project.version}.war 

                    to the build dir -->

                  <groupId>eu.etaxonomy</groupId>

                  <artifactId>cdm-webapp</artifactId>

                  <version>${project.version}</version>

                  <type>war</type>

                  <!-- <classifier> [classifier - optional] </classifier> -->

                  <overWrite>true</overWrite>

                  <destFileName>cdm-webapp-${project.version}.war</destFileName>

                  <outputDirectory>

                    ${project.build.directory}

                  </outputDirectory>

                </artifactItem>

              </artifactItems>

            </configuration>

          </execution>

        </executions>

      </plugin>

      <!-- ====== PACKAGE ====== -->

      <!-- package the default webapp, // (and also add the cdm-webapp.war) 

        test with: mvn war:war -->

      <plugin>

        <groupId>org.apache.maven.plugins</groupId>

        <artifactId>maven-war-plugin</artifactId>

        <version>3.3.2</version>

        <configuration>

          <warName>default-webapp</warName>

          <packagingExcludes>

            cdm-webapp-*.war

          </packagingExcludes>

          <!-- <overlays> <overlay> <groupId>eu.etaxonomy</groupId> <artifactId>cdm-webapp</artifactId> 

            <!- - version is set in dependency - -> <skip>true</skip> <!- - Do Not overlay 

            - -> </overlay> </overlays> -->

        </configuration>

        <executions>

          <execution>

            <phase>package</phase>

            <goals>

              <goal>war</goal>

            </goals>

          </execution>

        </executions>

      </plugin>

      <plugin>

        <!-- Assemble the runnable server jar test with: mvn assembly:single -->

        <groupId>org.apache.maven.plugins</groupId>

        <artifactId>maven-assembly-plugin</artifactId>

        <version>3.3.0</version>

        <configuration>

          <appendAssemblyId>false</appendAssemblyId>

          <descriptors>

            <descriptor>src/main/assembly/assembly.xml</descriptor>

          </descriptors>

          <archive>

            <manifest>

              <mainClass>eu.etaxonomy.cdm.server.Bootloader</mainClass>

              <addDefaultImplementationEntries>true</addDefaultImplementationEntries>

              <addDefaultSpecificationEntries>true</addDefaultSpecificationEntries>

            </manifest>

          </archive>

        </configuration>

        <executions>

          <execution>

            <id>make-assembly</id>

            <phase>package</phase>

            <goals>

              <goal>single</goal>

            </goals>

          </execution>

        </executions>

      </plugin>

      <plugin>

        <!-- ====== INSTALL ====== -->

        <!-- Build a Debian package -->

        <groupId>org.apache.maven.plugins</groupId>

        <artifactId>maven-antrun-plugin</artifactId>

        <version>3.0.0</version>

        <executions>

          <execution>

            <phase>install</phase>

            <configuration>

              <target>

                <property name="project.fullversionstring" value="${project.version}" />

                <property name="project.version" value="${project.version}" />

                <ant antfile="${project.basedir}/src/main/installer/linux/build-deb.xml" dir="${project.basedir}" />

              </target>

            </configuration>

            <goals>

              <goal>run</goal>

            </goals>

          </execution>

        </executions>

      </plugin>

      <!-- Build windows installer -->

      <!-- temporarily switched off due to problems with jenkins build after upgrading to debian 10 (#9972)  -->

 <!--     <plugin>

        <groupId>org.codehaus.mojo</groupId>

        <artifactId>exec-maven-plugin</artifactId>

        <version>3.0.0</version>

        <executions>

          <execution>

            <phase>install</phase>

            <goals>

              <goal>exec</goal>

            </goals>

          </execution>

        </executions>

        <configuration>

          <executable>makensis</executable>   -->

          <!-- optional -->

    <!--      <workingDirectory>/tmp</workingDirectory>

          <arguments>    -->

            <!-- <argument>-V3</argument> -->

 <!--           <argument>${project.basedir}/target/installer/win32/setup.nsi</argument>

          </arguments>s

        </configuration>

      </plugin> -->

      <!-- Build Docker image -->

      <plugin>

        <groupId>io.fabric8</groupId>

        <artifactId>docker-maven-plugin</artifactId>

        <version>0.38.1</version>

        <configuration>

          <images>

            <image>

              <!-- docker hub does not allow dots in organizations, so the name is

                    just 'cybertaxonomy', this MUST NOT BE CHANGED!!!!  -->

              <name>cybertaxonomy/${project.artifactId}:${project.version}</name>

              <build>

                <!-- use a Dockerfile in the directory src/main/docker/production -->

                <dockerFileDir>production</dockerFileDir>

                <!-- fabric8-maven-plugin filters given Dockerfile with Maven properties -->

                 <!-- For example, the default <filter>${*}</filter> parse Maven properties 

                     in the format that we know. If you specify a single character for 

                     <filter> then this delimiter is taken for both, the start and the end. 

                     E.g a <filter>@</filter> triggers on parameters in the format @…​@, -->

                <filter>@</filter>

                <assembly>

                  <descriptorRef>artifact</descriptorRef>

                    <!--

                         1. The maven plugin copies the jar to the artifacts assembly location at:

                            ./target/docker/eu.etaxonomy/cdm-server/${project.version}/build/maven/cdm-server-${project.version}.jar

                         2. a tar is being created at target/docker/eu.etaxonomy/cdm-server/${project.version}/tmp/docker-build.tar 

                            which contains all files located in /target/docker/production and the artifacts. 

                            Artifacts are put into the folder maven/ inside the tar archive

                         3. The tar archive is passed to the docker daemon and is used as working directory for the build 

                     -->

                  </assembly>

              </build>

               <!-- TODO the run configuration if needed, see src/main/docker/production/README for examples -->

               <!-- 

               <run>

                 <ports>8080:8080</ports>

               </run>

                -->

             </image>

           </images>

        </configuration>

        <!-- Connect start/stop to pre- and

             post-integration-test phase, respectively if you want to start

             your docker containers during integration tests -->

        <executions/>

      </plugin>

      <!-- ====== DEPLOY ====== -->

      <plugin>

        <groupId>org.apache.maven.plugins</groupId>

        <artifactId>maven-deploy-plugin</artifactId>

        <version>2.8.2</version>

      </plugin>

      <plugin>

        <!-- groupId>ch.dvbern.oss.maven.jgitflow</groupId>

        <artifactId>jgitflow-maven-plugin</artifactId>

        <version>1.0-m8</version>  -->

        <groupId>external.atlassian.jgitflow</groupId>

        <artifactId>jgitflow-maven-plugin</artifactId>

        <version>1.0-m6</version>

        <configuration>

          <pushHotfixes>true</pushHotfixes>

          <pushReleases>true</pushReleases>

          <enableSshAgent>true</enableSshAgent>

          <allowSnapshots>true</allowSnapshots>

          <allowUntracked>true</allowUntracked>

        </configuration>

        <dependencies>

          <!-- 

                upgrading dependency jsch.agent.version of jgit-flow plugin to 0.1.53 

                in order to have ssl key exchange algorithms compatible with openssh 6.7 

             -->

          <dependency>

            <groupId>com.jcraft</groupId>

            <artifactId>jsch</artifactId>

            <version>0.1.55</version>

          </dependency>

        </dependencies>

      </plugin>

      <plugin>

        <groupId>org.codehaus.mojo</groupId>

        <artifactId>wagon-maven-plugin</artifactId>

        <version>1.0</version>

        <!-- Problems with the wagon-maven-plugin have been encounterd on 

          Windows, it should work properly on linux though. -->

        <executions>

          <execution>

            <phase>deploy</phase>

            <goals>

              <goal>upload</goal>

            </goals>

          </execution>

        </executions>

        <configuration>

          <fromDir>target</fromDir>

          <includes>*${project.version}*.deb,*${project.version}*.jar,*${project.version}*.exe</includes>

          <url>scpexe://wp5.e-taxonomy.eu/var/www/download/cdmserver/${project.version}</url>

          <serverId>wp5.e-taxonomy.eu</serverId>

        </configuration>

      </plugin>

    </plugins>

    <!-- EXTENSIONS -->

    <extensions>

      <extension>

        <groupId>org.apache.maven.wagon</groupId>

        <artifactId>wagon-scm</artifactId>

        <version>3.5.1</version>

      </extension>

      <extension>

        <groupId>org.apache.maven.wagon</groupId>

        <artifactId>wagon-ssh</artifactId>

        <version>3.5.1</version>

      </extension>

      <extension>

        <groupId>org.apache.maven.wagon</groupId>

        <artifactId>wagon-ssh-external</artifactId>

        <version>3.5.1</version>

      </extension>

      <extension>

        <groupId>org.apache.maven.scm</groupId>

        <artifactId>maven-scm-manager-plexus</artifactId>

        <version>1.12.2</version>

      </extension>

      <extension>

        <groupId>org.apache.maven.scm</groupId>

        <artifactId>maven-scm-provider-svnexe</artifactId>

        <version>1.12.2</version>

      </extension>

      <!-- WebDAV plugin to upload snapshots -->

      <extension>

        <groupId>org.apache.maven.wagon</groupId>

        <artifactId>wagon-webdav-jackrabbit</artifactId>

        <version>3.5.1</version>

      </extension>

    </extensions>

  </build>

  <reporting>

    <plugins>

      <plugin>

        <!-- you will want to start by publishing your classes' Javadocs -->

        <groupId>org.apache.maven.plugins</groupId>

        <artifactId>maven-javadoc-plugin</artifactId>

        <version>3.3.1</version>

        <configuration>    

          <doclint>${doclint}</doclint>

        </configuration>

      </plugin>

      <plugin>

        <!-- this will generate an indexed and cross-referenced HTML version 

          of your source code -->

        <groupId>org.apache.maven.plugins</groupId>

        <artifactId>maven-jxr-plugin</artifactId>

        <version>2.5</version>

      </plugin>

      <plugin>

        <!-- if you use @todo tags to remind you of things to be done (which 

          is a good coding practice), the taglist report will generate a list of all 

          the items marked @todo or TODO -->

        <groupId>org.codehaus.mojo</groupId>

        <artifactId>taglist-maven-plugin</artifactId>

        <version>2.4</version>

      </plugin>

      <plugin>

        <!-- Test coverage can be a useful indication of the quality of your 

          unit tests. It basically tells you how much of your code is actually run 

          by your unit tests, which, in turn, can give you a good idea of the tests' 

          quality -->

        <groupId>org.codehaus.mojo</groupId>

        <artifactId>cobertura-maven-plugin</artifactId>

        <version>2.7</version>

      </plugin>

    </plugins>

  </reporting>

  <!-- DISTRIBUTION MANAGEMENT -->

  <distributionManagement>

    <site>

      <id>wp5.e-taxonomy.eu</id>

      <url>

        scpexe://wp5.e-taxonomy.eu/var/www/wp5.e-taxonomy.eu/cdm-server

      </url>

    </site>

    <repository>

      <uniqueVersion>false</uniqueVersion>

      <id>wp5.e-taxonomy.eu</id>

      <name>Edit Maven Repository</name>

      <url>

        scpexe://wp5.e-taxonomy.eu/var/www/wp5.e-taxonomy.eu/mavenrepo

      </url>

    </repository>

  </distributionManagement>

  <dependencyManagement>

    <dependencies>

      <dependency>

        <groupId>org.slf4j</groupId>

        <artifactId>slf4j-api</artifactId>

        <version>${slf4j.version}</version>

      </dependency>

    </dependencies>

  </dependencyManagement>

  <dependencies>

    <!-- maven 3 no longer supports uniqueVersions for SNAPSHOT artifacts. 

      The cdm-server Bootlader however relies on a specific name of the cdm-webapp 

      war file. In order to achieve this with maven 3 the below dependency is now 

      handled more explicitely by utilizing the dependency:copy-dependencies goal 

      in the build/plugins section -->

      <!-- <dependency> -->

      <!--   <groupId>eu.etaxonomy</groupId>  -->

      <!--   <artifactId>cdm-webapp</artifactId> -->

      <!--   <version>${project.version}</version>  -->

      <!--   <type>war</type> -->

      <!-- </dependency> -->

    <!-- JETTY -->

    <dependency>

      <groupId>org.eclipse.jetty</groupId>

      <artifactId>jetty-webapp</artifactId>

      <version>${jetty-version}</version>

    </dependency>

    <dependency>

        <groupId>org.eclipse.jetty</groupId>

        <artifactId>jetty-webapp-logging</artifactId>

        <version>9.4.20.v20190813</version><!-- versioning independent of jetty core -->

        <type>pom</type><!-- we only need the dependencies like jul-to-slf4j managed in this pom! -->

        <!-- this is for log4j12 ,el-api

         still need to check if this is really needed by jetty 

        <exclusions>

          <exclusion>

            <groupId>org.slf4j</groupId>

            <artifactId>log4j-over-slf4j</artifactId>

          </exclusion>

        </exclusions> -->

    </dependency>

    <dependency>

      <groupId>org.eclipse.jetty</groupId>

      <artifactId>jetty-plus</artifactId>

      <version>${jetty-version}</version>

    </dependency>

    <dependency>

      <groupId>org.eclipse.jetty</groupId>

      <artifactId>jetty-jmx</artifactId>

      <version>${jetty-version}</version>

    </dependency>

    <dependency>

      <groupId>org.eclipse.jetty</groupId>

      <artifactId>jetty-security</artifactId>

      <version>${jetty-version}</version>

    </dependency>

    <dependency>

      <groupId>org.eclipse.jetty</groupId>

      <artifactId>jetty-annotations</artifactId>

      <version>${jetty-version}</version>

    </dependency>

    <dependency>

      <groupId>org.eclipse.jetty</groupId>

      <artifactId>apache-jsp</artifactId>

      <version>${jetty-version}</version>

      <type>jar</type>

    </dependency>

    <dependency>

      <groupId>org.eclipse.jetty</groupId>

      <artifactId>apache-jstl</artifactId>

      <version>${jetty-version}</version>

      <type>pom</type>

    </dependency>

 <!--   <dependency>

       <groupId>jakarta.el</groupId>

       <artifactId>jakarta.el-api</artifactId>

       <version>4.0.0</version>

    </dependency>   -->

    <dependency>

      <groupId>javax.transaction</groupId>

      <artifactId>jta</artifactId>

      <version>1.1</version>

    </dependency>

    <!-- JSON -->

    <dependency>

      <!-- according to maven repo this artifact moved to com.fasterxml.jackson.core » jackson-databind

        but changing to next higher version 2.0.0 throws exceptions on the jsp pages (e.g. .../cdmserver/instances.jsp) -->

      <groupId>org.codehaus.jackson</groupId>

      <artifactId>jackson-mapper-asl</artifactId>

      <version>1.9.13</version>

    </dependency>

    <!-- windows service -->

    <dependency>

      <groupId>tanukisoft</groupId>

      <artifactId>wrapper</artifactId>

      <version>3.2.3</version>

    </dependency>

    <!-- Logging -->

    <dependency>

      <groupId>org.slf4j</groupId>

      <artifactId>slf4j-api</artifactId>

    </dependency>

    <!-- move all logging to log4j 2-->

    <!-- <dependency>

      <groupId>org.apache.logging.log4j</groupId>

      <artifactId>log4j-slf4j-impl</artifactId>

      <version>${log4j.version}</version>

    </dependency>  -->

    <!-- move all log4j2 logging to the current slf4j implementor,

         !!! never use together with log4j-slf4j-impl on classpath => endless circle -->

    <dependency>

      <groupId>org.apache.logging.log4j</groupId>

      <artifactId>log4j-to-slf4j</artifactId>

      <version>${log4j.version}</version>

    </dependency>

    <dependency>

      <groupId>org.apache.logging.log4j</groupId>

      <artifactId>log4j-core</artifactId>

      <version>${log4j.version}</version>

    </dependency>

    <dependency>

      <groupId>commons-cli</groupId>

      <artifactId>commons-cli</artifactId>

      <version>1.3.1</version>

    </dependency>

    <dependency>

      <groupId>commons-io</groupId>

      <artifactId>commons-io</artifactId>

      <version>2.11.0</version>

    </dependency>

    <dependency>

      <!-- only used in InstanceManager class -->

      <groupId>org.apache.commons</groupId>

      <artifactId>commons-collections4</artifactId>

      <version>4.4</version>

    </dependency>

    <dependency>

      <groupId>net.sf.jopt-simple</groupId>

      <artifactId>jopt-simple</artifactId>

      <version>5.0.4</version>

    </dependency>

    <!-- Database dependencies -->

    <dependency>

      <groupId>eu.etaxonomy</groupId>

      <artifactId>cdmlib-db</artifactId>

      <version>5.5.1</version>

    </dependency>

  </dependencies>

</project>