EDIT

<?xml version="1.0" encoding="UTF-8"?>

  <artifactId>cdm-webapp</artifactId>

  <groupId>eu.etaxonomy</groupId>

  <name>CDM Webapp</name>

  <properties>

    <cdm.vaadin.version>5.18.0-SNAPSHOT</cdm.vaadin.version>

  <repositories>

    <!-- the cdm internal repository -->

    <repository>

      <id>EditRepository</id>

        <enabled>true</enabled>

        <updatePolicy>always</updatePolicy>

      </releases>

      <snapshots>

        <enabled>true</enabled>

        <updatePolicy>always</updatePolicy>

      </snapshots>

  </repositories>

  <distributionManagement>

    <repository>

      <uniqueVersion>false</uniqueVersion>

    </repository>

  </distributionManagement>

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

      <groupId>eu.etaxonomy</groupId>

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

    </dependency>

      <groupId>eu.etaxonomy</groupId>

      <version>${cdm.vaadin.version}</version>

    </dependency>

      <groupId>eu.etaxonomy</groupId>

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

      <scope>test</scope>

  </dependencies>

    <plugins>

      <plugin>

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

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

          <overlays>

            <!-- 

                Overlays are applied with a first-win strategy. 

                Overlays are applied in the order in which they are defined in the <overlays> configuration. 

                in contrast is expected to be build only due to changes in the vaadin specific 

                that only the cdmlib-jars from cdm-remote-webapp can make their way into the final

                war.    

            <overlay>

            <overlay>

              <groupId>eu.etaxonomy</groupId>

                <exclude>WEB-INF/lib/cdmlib-*.jar</exclude>

              </excludes>

            <overlay>

              <!-- overlay a second time to only add cdmlib-cache.jar -->

              <groupId>eu.etaxonomy</groupId>

              <artifactId>cdm-vaadin</artifactId>

          </overlays>

      </plugin>

        resources are accumulating and must be deleted before entering the prepare-package

        life cycle phase, therefore configuring this auto-clean makes a lot of sense.

        it is called twice and thus removes the cdm-webapp-x.x.x.war after it has been build,

        maven then fails with : "The packaging for this project did not assign a file to the build artifact"

        Therefore this is disabled! 

        as long as this plugin is defined before the maven-dependency-plugin the clean should only

        happen before the unpack, see http://www.mkyong.com/maven/maven-plugin-execution-order-in-same-phase/

        Maybe it makes sense to define a fileset that only includes the unpacked war files  

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

        <artifactId>maven-clean-plugin</artifactId>

        <version>2.5</version>

        <executions>

          <execution>

            <id>auto-clean</id>

            <phase>initialize</phase>

            <goals>

              <goal>clean</goal>

            </goals>

          </execution>

        </executions>

      </plugin>

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

          <pushHotfixes>true</pushHotfixes>

          <allowSnapshots>true</allowSnapshots>

          <allowUntracked>true</allowUntracked>

        </configuration>

        <dependencies>

          <!-- 

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

                in order have ssl key exchange algorithms compatible with openssh 6.7 

            <groupId>com.jcraft</groupId>

            <artifactId>jsch</artifactId>

            <version>0.1.53</version>

          </dependency>

        </dependencies>

      </plugin>

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

        <artifactId>maven-enforcer-plugin</artifactId>

        <version>3.0.0-M2</version>

        <executions>

          <execution>

            <id>enforce</id>

            <configuration>

              <fail>true</fail>

              <skip>false</skip>

              <rules>

                </requireMavenVersion>

              </rules>

            </configuration>

            <goals>

              <goal>enforce</goal>

            </goals>

          </execution>

        </executions>

      </plugin>

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

        <artifactId>wagon-scm</artifactId>

      <extension>

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

        <artifactId>wagon-ssh</artifactId>

      <extension>

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

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

    </extensions>

  </build>

</project>