EDIT

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

    <jetty-version>9.2.5.v20141112</jetty-version>

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

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

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

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

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

      <id>EditLocalRepository</id>

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

        cdmlib-remote-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>

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

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

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

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

                    to the build dir -->

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

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

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

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

                <property name="project.fullversionstring"

                  value="${project.version}" />

                <ant

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

                  dir="${project.basedir}" />

      <!-- potentialy needed for maven 3 <plugin> <groupId>org.apache.maven.plugins</groupId> 

        <artifactId>maven-depoly-plugin</artifactId> <version>2.7</version> <dependencies> 

        <dependency> <groupId>org.apache.maven.wagon</groupId> <artifactId>wagon-ssh</artifactId> 

        <version>1.0-beta-7</version> </dependency> </dependencies> </plugin> -->

          <goals>deploy</goals><!-- skipping site-deploy by explicitly configuring 

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

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

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

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

        <!-- 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' 

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

      The cdm-server Bootlader however relies on a specific name of the cdmlib-remote-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 gloal 

      in the build/plugins section <dependency> <groupId>eu.etaxonomy</groupId> 

      <artifactId>cdmlib-remote-webapp</artifactId> <version>${project.version}</version> 

      <type>war</type> </dependency> -->

    <dependency>

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

      <artifactId>jetty-annotations</artifactId>

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

    </dependency>

    <dependency>

      <groupId>commons-collections</groupId>

      <artifactId>commons-collections</artifactId>

      <version>3.2.1</version>

    </dependency>

        org.eclipse.jetty.webapp.Configuration.ClassList classlist = org.eclipse.jetty.webapp.Configuration.ClassList.setServerDefault(server);

        classlist.addAfter("org.eclipse.jetty.webapp.FragmentConfiguration", "org.eclipse.jetty.plus.webapp.EnvConfiguration", "org.eclipse.jetty.plus.webapp.PlusConfiguration");

        classlist.addBefore("org.eclipse.jetty.webapp.JettyWebXmlConfiguration", "org.eclipse.jetty.annotations.AnnotationConfiguration");

            server.addEventListener(mBeanContainer);

            server.addBean(Log.getLog());            

<web-app xmlns="http://java.sun.com/xml/ns/javaee"

      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

      xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd"

      version="3.0">