maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Scholte (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SUREFIRE-1683) Buildfix: TLS 1.2 passed to maven-invoker-plugin via system property
Date Fri, 26 Jul 2019 12:43:00 GMT

    [ https://issues.apache.org/jira/browse/SUREFIRE-1683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16893800#comment-16893800
] 

Robert Scholte commented on SUREFIRE-1683:
------------------------------------------

Well, maybe you're looking referring to a different thread, but I did mention how https.protocols
should work.
And there's actually no need for a profile either. There should be no default value for https.protocols.
In case of JDK7 if you don't set if via commandline and you have an empty repository, you're
already doomed. So you must set https.protocols, and with the configuration on maven-invoker-plugin
it'll be pikced up automatically.
This is the cleanest and most compact solution and has proven itself for about a year.


> Buildfix: TLS 1.2 passed to maven-invoker-plugin via system property
> --------------------------------------------------------------------
>
>                 Key: SUREFIRE-1683
>                 URL: https://issues.apache.org/jira/browse/SUREFIRE-1683
>             Project: Maven Surefire
>          Issue Type: Task
>            Reporter: Tibor Digana
>            Assignee: Tibor Digana
>            Priority: Major
>             Fix For: 3.0.0-M4
>
>
> Setting system property "https.protocols" to "TLSv1.2" on :maven-invoker-plugin" in the
project module "maven-failsafe-plugin".



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

Mime
View raw message