OpenTracing TCK fails due to Maven Central banning insecure connections

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.