summaryrefslogtreecommitdiff
path: root/java/perftests/pom.xml
diff options
context:
space:
mode:
authorRobert Greig <rgreig@apache.org>2007-01-15 17:29:32 +0000
committerRobert Greig <rgreig@apache.org>2007-01-15 17:29:32 +0000
commita83817a1f39a471272494e28d059373d6a6f77df (patch)
treed66ba37dee96c5bbe25a41476dbc672b0e80de64 /java/perftests/pom.xml
parent23ad76b344c064a926152a6728b0838bbf446f22 (diff)
downloadqpid-python-a83817a1f39a471272494e28d059373d6a6f77df.tar.gz
(Patch submitted by Rupert Smith) QPID-297
There were junit exclusions in the POM files that were causing junit to not be found when compiling tests. This may be a maven bug, but a better solution is to exclude stuff in assembly descriptors instead. git-svn-id: https://svn.apache.org/repos/asf/incubator/qpid/trunk/qpid@496414 13f79535-47bb-0310-9956-ffa450edef68
Diffstat (limited to 'java/perftests/pom.xml')
-rw-r--r--java/perftests/pom.xml24
1 files changed, 23 insertions, 1 deletions
diff --git a/java/perftests/pom.xml b/java/perftests/pom.xml
index 98d2696b80..bfa24d99a3 100644
--- a/java/perftests/pom.xml
+++ b/java/perftests/pom.xml
@@ -38,10 +38,32 @@
</properties>
<dependencies>
+
<dependency>
<groupId>org.apache.qpid</groupId>
<artifactId>qpid-client</artifactId>
</dependency>
+
+ <dependency>
+ <groupId>log4j</groupId>
+ <artifactId>log4j</artifactId>
+ </dependency>
+
+ <!-- Here JUnit is a deliberate 'compile' scope dependency, it will be packaged with the perf testing tools. -->
+ <dependency>
+ <groupId>junit</groupId>
+ <artifactId>junit</artifactId>
+ <scope>compile</scope>
+ </dependency>
+
+ <!-- Will be added to maven repo soon. JUnit test runner that can add repeats/concurrenct/timing etc to tests.
+ <dependency>
+ <groupId>uk.co.thebadgerset</groupId>
+ <artifactId>junit-toolkit</artifactId>
+ <scope>compile</scope>
+ </dependency>
+ -->
+
</dependencies>
<build>
@@ -54,7 +76,7 @@
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-surefire-plugin</artifactId>
<configuration>
- <skip>true</skip>
+ <!--<skip>true</skip>-->
</configuration>
</plugin>