[
https://issues.apache.org/jira/browse/MNG-7685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17686799#comment-17686799
]
John Patrick commented on MNG-7685:
-----------------------------------
{{So using -Dmaven.resolver.transport=wagon
-Dmaven.wagon.http.ssl.insecure=true. And builds have started to pass.}}
{{So looking at HttpClient 4.x and also the comments above, am I correct that
purely via properties it isn't possible to achieve the same logic. We would
need to add a new custom property which toggles new custom config.}}
> Unable to ignore certificate errors with v3.9.0
> -----------------------------------------------
>
> Key: MNG-7685
> URL: https://issues.apache.org/jira/browse/MNG-7685
> Project: Maven
> Issue Type: Bug
> Components: Core
> Affects Versions: 3.9.0
> Environment: Linux and Mac
> Reporter: John Patrick
> Priority: Major
> Labels: Regression
>
> Setting `-Dmaven.wagon.http.ssl.insecure=true` via `.mvn/jvm.config` does not
> work with v3.9.0, but works with v3.8.7. i.e. when executing `./mvnw
> org.apache.maven.plugins:maven-dependency-plugin:3.5.0:go-offline`.
> I've got a minishift instance running jenkins, with agents created on demand.
> I've got a nexus with a self signed certificate and for simpler out of the
> box Jenkins agents I'm happy for it to ignore the nexus certificate error. So
> Jenkins uses config-file-provider plugin to provide `jvm.config` and for
> builds to ignore certificate issues.
> Not sure if maven has;
> # stopped reading `.mvn/jvm.config`
> # stoped allowing multiple line `.mvn/jvm.config`
> # not setting System properties as defined in `.mvn/jvm.config`
> # wagon upgrade has introduced bug or new config
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
