This is an automated email from the ASF dual-hosted git repository.
aledsage pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/brooklyn-server.git
commit 890ef568a1a710d62f0cbd160a8d0123b4655536
Author: Paul Campbell <paul.campb...@cloudsoft.io>
AuthorDate: Mon Oct 8 17:06:58 2018 +0100
Bump assertj from 2.2.0 to 3.11.1
As brooklyn is now built with Java 8 (brooklyn-server/pom.xml java.version =
1.8) there is no reason not to take advantage of the improved fluent
assertions
in assertj 3.x.
---
parent/pom.xml | 5 +++++
pom.xml | 2 +-
2 files changed, 6 insertions(+), 1 deletion(-)
diff --git a/parent/pom.xml b/parent/pom.xml
index 971c76e..e0e2633 100644
--- a/parent/pom.xml
+++ b/parent/pom.xml
@@ -581,6 +581,11 @@
<groupId>org.ops4j.pax.web</groupId>
<artifactId>pax-web-spi</artifactId>
<version>${pax-web.version}</version>
+ </dependency>
+ <dependency>
+ <groupId>org.assertj</groupId>
+ <artifactId>assertj-core</artifactId>
+ <version>${assertj.version}</version>
</dependency>
</dependencies>
</dependencyManagement>
diff --git a/pom.xml b/pom.xml
index 20c0bc8..8b5f56b 100644
--- a/pom.xml
+++ b/pom.xml
@@ -187,7 +187,7 @@
<surefire.version>2.19.1</surefire.version>
<testng.version>6.10</testng.version>
<mockito.version>2.7.12</mockito.version>
- <assertj.version>2.2.0</assertj.version> <!-- v 2.2.0 is being used as
v 3.20 introduces Java8 dependencies-->
+ <assertj.version>3.11.1</assertj.version>
<hamcrest.version>1.1</hamcrest.version>
<mockwebserver.version>20121111</mockwebserver.version>
