Dropwizard reporter: use embedded hawkular/wildfly for integration tests

Remove existing config with docker
hawkular · Feb 23, 2017 · 76bcdab · 76bcdab
1 parent 54ced04
commit 76bcdab
Show file tree

Hide file tree

Showing 8 changed files with 207 additions and 255 deletions.
diff --git a/clients/dropwizard/.travis.install.maven.sh b/clients/dropwizard/.travis.install.maven.sh
diff --git a/clients/dropwizard/.travis.maven.settings.xml b/clients/dropwizard/.travis.maven.settings.xml
diff --git a/clients/dropwizard/.travis.yml b/clients/dropwizard/.travis.yml
diff --git a/clients/dropwizard/.travis/wait_for_services.rb b/clients/dropwizard/.travis/wait_for_services.rb
diff --git a/clients/dropwizard/README.md b/clients/dropwizard/README.md
@@ -11,7 +11,7 @@ To use the Hawkular Dropwizard Reporter in any Java application:
     <dependency>
         <groupId>org.hawkular.metrics</groupId>
         <artifactId>hawkular-dropwizard-reporter</artifactId>
-        <version>0.24.0</version>
+        <version>0.25.0</version>
     </dependency>
 ````
 
@@ -80,7 +80,7 @@ You must also add a module dependency to hawkular-dropwizard-reporter-factory (i
     <dependency>
         <groupId>org.hawkular.metrics</groupId>
         <artifactId>hawkular-dropwizard-reporter-factory</artifactId>
-        <version>0.24.0</version>
+        <version>0.25.0</version>
     </dependency>
 ````
 

diff --git a/clients/dropwizard/docker-compose.yml b/clients/dropwizard/docker-compose.yml