<!-- logging dependencies (managed by parent pom, don't set versions or scopes here) -->
<dependency>
<groupId>org.slf4j</groupId>
<artifactId>slf4j-api</artifactId>
</dependency>
<!-- binding for log4j2, scope=runTime set in parent pom -->
<dependency>
<groupId>org.apache.logging.log4j</groupId>
<artifactId>log4j-slf4j-impl</artifactId>
</dependency>
<dependency>
<groupId>org.apache.logging.log4j</groupId>
<artifactId>log4j-api</artifactId>
</dependency>
<dependency>
<groupId>org.apache.logging.log4j</groupId>
<artifactId>log4j-core</artifactId>
</dependency>
</dependencies>
<description>A module which only has the purpose to run slow running integration tests.
They can be executed by calling
mvn verify</description>
<build>
<plugins>
<plugin>
<artifactId>maven-failsafe-plugin</artifactId>
<executions>
<execution>
<goals>
<goal>integration-test</goal>
<goal>verify</goal>
</goals>
</execution>
</executions>
</plugin>
<!-- integrationtest module shouldn't create a jar file (it would be empty).
Recipe from https://stackoverflow.com/questions/2188746/what-is-the-best-way-to-avoid-maven-jar
- JD 2018-03-08 -->
<!-- I had to comment this out because the gpg plugin would error on trying to sign the inexistent jar when doing 'mvn release:perform' or 'mvn package gpg:sign',
see https://github.com/biojava/biojava/issues/727 - JD 2018-03-23
-->
<!--
<plugin>
<artifactId>maven-jar-plugin</artifactId>
<executions>
<execution>
<id>default-jar</id>
<phase>none</phase>
<configuration>
<finalName>unwanted</finalName>
<classifier>unwanted</classifier>
</configuration>
</execution>
</executions>
</plugin>
<plugin>
<artifactId>maven-install-plugin</artifactId>
<executions>
<execution>
<id>default-install</id>
<phase>none</phase>
</execution>
</executions>
</plugin>
-->
<!-- With this 'mvn deploy' should not publish the jar file. See https://github.com/biojava/biojava/issues/727 - JD 2018-03-23 -->