Please change

<https.protocols>TLSv1.2</https.protocols>

to

<https.protocols>${https.protocols}</https.protocols>

so it is only set when required, and we don't need to update the tests when there are new requirements for https protocols.

thanks,
Robert

On Thu, 25 Jul 2019 00:17:44 +0200, <tibordig...@apache.org> wrote:

This is an automated email from the ASF dual-hosted git repository.

tibordigana pushed a commit to branch TLS1.2
in repository https://gitbox.apache.org/repos/asf/maven-surefire.git

commit 6425a679178d8ca73993d475eb800e82f4213900
Author: tibordigana <tibordig...@apache.org>
AuthorDate: Thu Jul 25 00:16:49 2019 +0200

    TLS 1.2 passed to maven-invoker-plugin via system property
---
 maven-failsafe-plugin/pom.xml | 1 +
 1 file changed, 1 insertion(+)

diff --git a/maven-failsafe-plugin/pom.xml b/maven-failsafe-plugin/pom.xml
index 2e85275..2bc4a14 100644
--- a/maven-failsafe-plugin/pom.xml
+++ b/maven-failsafe-plugin/pom.xml
@@ -334,6 +334,7 @@
                                     <properties>
                                         
<integration-test-port>${failsafe-integration-test-port}</integration-test-port>
                                         
<integration-test-stop-port>${failsafe-integration-test-stop-port}</integration-test-stop-port>
+ <https.protocols>TLSv1.2</https.protocols>
                                     </properties>
                                 </configuration>
                             </execution>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Reply via email to