From 2109f14c24f90df3f43aee7f3248ac59e6088735 Mon Sep 17 00:00:00 2001 From: Norman Maurer Date: Wed, 17 Oct 2018 19:36:20 +0200 Subject: [PATCH] When running our testsuite with netty-tcnative-boringssl-static we should use an empty classifier. (#8396) Motivation: We publish an "uber-jar" for netty-tcnative-boringssl-static so we should use it when testing against boringssl. Modifications: Ensure we use empty classifier. Result: Use uber-jar when testing --- docker/docker-compose.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docker/docker-compose.yaml b/docker/docker-compose.yaml index ceb5a8791c..65fffba038 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 -Dtcnative.artifactId=netty-tcnative-boringssl-static" + command: /bin/bash -cl "./mvnw clean install -Dio.netty.testsuite.badHost=netty.io -Dtcnative.artifactId=netty-tcnative-boringssl-static -Dtcnative.classifier=" shell: <<: *common