[jboss-jira] [JBoss JIRA] (WFLY-12984) OpenTracing TCK fails due to Maven Central banning insecure connections

[James Perkins (Jira)]

    [ https://issues.redhat.com/browse/WFLY-12984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13950757#comment-13950757 ] 

James Perkins commented on WFLY-12984:
--------------------------------------

Note when the first PR is merged we should probably put this back to open so we can follow up with a real fix. Or we could create a new JIRA.

> OpenTracing TCK fails due to Maven Central banning insecure connections
> -----------------------------------------------------------------------
>
>                 Key: WFLY-12984
>                 URL: https://issues.redhat.com/browse/WFLY-12984
>             Project: WildFly
>          Issue Type: Task
>          Components: MP OpenTracing, Test Suite
>            Reporter: James Perkins
>            Assignee: James Perkins
>            Priority: Critical
>             Fix For: 19.0.0.Beta1
>
>
> The Microprofile OpenTracing TCK fails as it uses the Shrinkwrap resolver to download dependencies. For currently unknown reasons this doesn't seem to honor the {{maven.repo.xxx}} properties or activated profiles. Some research needs to be done in order to figure out why this is.
> The workaround is to temporarily override the Shrinkwrap Resolver and use 3.1.4 which has a fix for the hard-coded http to https fix. See https://github.com/shrinkwrap/resolver/pull/115.



--
This message was sent by Atlassian Jira
(v7.13.8#713008)