简体   繁体   English

编译失败 - 无法从 https://maven.repository.redhat.com/ga/javax/servlet/javax.servlet-api/maven-metadata.xml 加载 Maven 元数据

[英]compile failing - Unable to load Maven meta-data from https://maven.repository.redhat.com/ga/javax/servlet/javax.servlet-api/maven-metadata.xml

Literally just hit up key in my command line to get the last command to compile my java project.从字面上看,只需在我的命令行中按下键即可获得编译我的 Java 项目的最后一个命令。 Is this a combination of updatePolicy and a server error on RedHat side?这是updatePolicy和 RedHat 端服务器错误的组合吗?

I'm not behind a proxy or anything, did not change anything.我没有支持代理或任何东西,没有改变任何东西。

Could not resolve all files for configuration ':compileClasspath'.

Could not resolve javax.servlet:javax.servlet-api:3.+.无法解析 javax.servlet:javax.servlet-api:3.+。 Required by: project : Failed to list versions for javax.servlet:javax.servlet-api.要求:项目:无法列出 javax.servlet:javax.servlet-api 的版本。 Unable to load Maven meta-data from https://maven.repository.redhat.com/ga/javax/servlet/javax.servlet-api/maven-metadata.xml .无法从https://maven.repository.redhat.com/ga/javax/servlet/javax.servlet-api/maven-metadata.xml加载 Maven 元数据。 Could not HEAD ' https://maven.repository.redhat.com/ga/javax/servlet/javax.servlet-api/maven-metadata.xml '.无法 HEAD ' https://maven.repository.redhat.com/ga/javax/servlet/javax.servlet-api/maven-metadata.xml '。 Received status code 500 from server: Internal Server Error从服务器收到状态代码 500:内部服务器错误

If this is an issue with RedHat though, I should be seeing more issues streaming in but I don't so it makes me believe it's an issue on my side but can't think of anything on my side.如果这是 RedHat 的问题,我应该会看到更多的问题,但我没有,所以这让我相信这是我这边的问题,但我想不出任何问题。

edit 1: in my build.gradle I can see maven { url "https://maven.repository.redhat.com/ga/" }编辑 1:在我的build.gradle我可以看到maven { url "https://maven.repository.redhat.com/ga/" }

can this be changed to an address that is not failing?这可以更改为不会失败的地址吗?

It looks like an issue on Redhat maven repository side, the server seems down: if you try to download manually some artefacts you also get 500 errors: eg : https://maven.repository.redhat.com/ga/javax/这看起来像是 Redhat maven 存储库方面的一个问题,服务器似乎关闭了:如果您尝试手动下载一些人工制品,您也会收到 500 个错误:例如: https : //maven.repository.redhat.com/ga/javax/

You can add other repositories in your repositories block :您可以在您的repositories块中添加其他存储repositories

repositories {
    jcenter()
    mavenCentral()

}

These two repositories should allow you to resolve all "standard" libraries in RELEASE version.这两个存储库应该允许您解析 RELEASE 版本中的所有“标准”库。 You did not specify in your question which version of the servlet-api you need, but it should be there.您没有在问题中指定您需要哪个版本的 servlet-api,但它应该在那里。

EDIT see https://access.redhat.com/articles/3620281 that can explain service down编辑https://access.redhat.com/articles/3620281 ,可以解释服务关闭

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

相关问题 Gradle 构建错误:无法从 https://repo1.maven.org/maven2/io/fabric/tools/gradle/maven-metadata.xml 加载 Maven 元数据 - Gradle Build Error: Unable to load Maven meta-data from https://repo1.maven.org/maven2/io/fabric/tools/gradle/maven-metadata.xml Maven自动删除依赖项版本(javax.servlet-api)中的尾随零 - Maven automatically removes trailing zeroes in dependency version (javax.servlet-api) Maven如何解决javax.servlet.servlet-api和javax.servlet.javax.servlet-api冲突 - how maven resolve javax.servlet.servlet-api and javax.servlet.javax.servlet-api conflict 如何使用其他javax.servlet-api? - How to use a different javax.servlet-api? Javax 持久性无法在 Maven 上编译 - Javax Persistence unable to compile on maven 无法在Netbeans中的Maven项目中导入任何javax-servlet - Unable to import any javax-servlet in Maven project in Netbeans 无法将Maven强制转换为javax.servlet.Filter - Maven cannot be cast to javax.servlet.Filter Maven:已部署javax.servlet规范 - Maven: javax.servlet specification deployed 如何强制Maven从中央存储库下载maven-metadata.xml? - How to force Maven to download maven-metadata.xml from the central repository? maven 尝试从存储库中检索错误的快照版本,因为 maven-metadata.xml - maven tries to retrieve wrong snapshot version from repository because of bad maven-metadata.xml
 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM