最近，在Jenkins中运行的Maven构建作业失败，出现以下异常，表示它们无法从Maven Central提取依赖项，应该使用HTTPS。我不知道如何将请求从HTTP更改为HTTPS。有人能指导我一下这件事吗?
[ERROR] Unresolveable build extension:
Plugin org.apache.maven.wagon:wagon-ssh:2.1 or one of its dependencies could not be resolved:
Failed to collect dependencies for org.apache.maven.wagon:wagon-ssh:jar:2.1 ():
Failed to read artifact descriptor for org.apache.maven.wagon:wagon-ssh:jar:2.1:
Could not transfer artifact org.apache.maven.wagon:wagon-ssh:pom:2.1 from/to central (http://repo.maven.apache.org/maven2):
Failed to transfer file: http://repo.maven.apache.org/maven2/org/apache/maven/wagon/wagon-ssh/2.1/wagon-ssh-2.1.pom.
Return code is: 501, ReasonPhrase:HTTPS Required. -> [Help 2]
Waiting for Jenkins to finish collecting data[ERROR]
Plugin org.apache.maven.plugins:maven-clean-plugin:2.4.1 or one of its dependencies could not be resolved:
Failed to read artifact descriptor for org.apache.maven.plugins:maven-clean-plugin:jar:2.4.1:
Could not transfer artifact org.apache.maven.plugins:maven-clean-plugin:pom:2.4.1 from/to central (http://repo.maven.apache.org/maven2):
Failed to transfer file: http://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-clean-plugin/2.4.1/maven-clean-plugin-2.4.1.pom.
Return code is: 501 , ReasonPhrase:HTTPS Required. -> [Help 1]
最初来自https://stackoverflow.com/a/59796324/32453，虽然这可能有用:
注意，你的父pom也可以(重新)定义存储库，如果它因为某种原因覆盖了central并指定了http，你就需要修复它(修复的地方:~/.m2/settings.xml)
还有父母。
如果你不能在父pom中修复它，你可以覆盖父pom的repo，就像这样，在你的子pom中(从3.6.3默认的超级pom中提取，似乎他们也从repo1中更改了名称):
<repositories>
<repository>
<id>central</id>
<name>Central Repository</name>
<url>https://repo.maven.apache.org/maven2</url> <!-- the https you've been looking for -->
<layout>default</layout>
<snapshots>
<enabled>false</enabled> <!-- or set to true if desired, default is false -->
</snapshots>
</repository>
</repositories>
使用Ubuntu 16.04, java 1.8.0_201。
我卸载了旧的maven，安装了maven 3.6.3，
仍然得到了Maven依赖失败的501错误。
意识到这可能是与要求https相关的信任库/密钥库问题。
发现现在可以使用jvm配置-Djavax选项。配置文件，请参见:https://maven.apache.org/configure.html。
因为我也在使用Tomcat，所以我从Tomcat (setenv.sh)中将密钥库和信任库配置复制到我的jvm中。配置，然后它工作!
还有一个选项可以在“export MAVEN_OPTS”中传递这个配置(当使用mvn generate时)，但尽管这阻止了501错误，但它创建了另一个:它期望一个pom文件。
创建一个单独的jvm。配置文件工作完美，只是把它放在你的项目的根。
希望这能帮助到一些人，我花了一整天才弄明白!
我也有同样的问题，但我用的是GitLab而不是Jenkins。我必须采取的步骤来克服这个问题:
My project is in GitLab so it uses the .yml file which points to a Docker image I have to do continuous integration, and the image it uses has the http://maven URLs. So I changed that to https://maven.
That same Dockerfile image had an older version of Maven 3.0.1 that gave me issues just overnight. I updated the Dockerfile to get the latest version 3.6.3
I then deployed that image to my online repository, and updated my Maven project ymlfile to use that new image.
And lastly, I updated my main projects POM file to reference https://maven... instead of http://maven
我意识到这更适合我的设置。但是如果不执行上述所有步骤，我仍然会继续得到这个错误消息
返回代码是:501,ReasonPhrase:HTTPS Required
