From b6522927d71d1c24e4e362165d5f70535046b5fe Mon Sep 17 00:00:00 2001 From: Norman Maurer Date: Sun, 28 Oct 2018 10:27:34 +0100 Subject: [PATCH] Add profile to easily run testsuite against netty-tcnative-boringssl-static (#8436) Motivation: We should provide an easy way to run our testsuite against netty-tcnative-boringssl-static Modifications: - Add boringssl profile which can be used to enable usage of netty-tcnative-boringssl-static - Make use of the profile in docker-compose Result: Cleaner and easier way of running testsuite against netty-tcnative-boringssl-static --- docker/docker-compose.yaml | 2 +- pom.xml | 7 +++++++ 2 files changed, 8 insertions(+), 1 deletion(-) diff --git a/docker/docker-compose.yaml b/docker/docker-compose.yaml index 3b8d5d0e22..f0183cd283 100644 --- a/docker/docker-compose.yaml +++ b/docker/docker-compose.yaml @@ -27,7 +27,7 @@ services: test-boringssl-static: <<: *common - command: /bin/bash -cl "./mvnw clean install -Dio.netty.testsuite.badHost=netty.io -Dxml.skip=true -Dtcnative.artifactId=netty-tcnative-boringssl-static -Dtcnative.classifier=" + command: /bin/bash -cl "./mvnw -P boringssl clean install -Dio.netty.testsuite.badHost=netty.io -Dxml.skip=true" shell: <<: *common diff --git a/pom.xml b/pom.xml index 78187ab3f8..c2b0e799f9 100644 --- a/pom.xml +++ b/pom.xml @@ -141,6 +141,13 @@ + + boringssl + + netty-tcnative-boringssl-static + + + leak