当前位置: 首页 > 知识库问答 >
问题:

升级到2019.3(CE)版本后,无法解析Intellij中的插件

房时铭
2023-03-14

我刚刚将Intellij从2019.2.x升级到2019.3,但在我的Java项目中发现了以下Maven插件错误。

Cannot resolve plugin org.codehaus.mojo:exec-maven-plugin:1.6.0
Cannot resolve plugin org.apache.maven.plugins:maven-resources-plugin:3.1.0
> Apache Maven 3.6.3  Maven home: /usr/local/Cellar/maven/3.6.3/libexec
> Java version: 11.0.2, vendor: Oracle Corporation, runtime:
/Library/Java/JavaVirtualMachines/jdk-11.0.2.jdk/Contents/Home Default
locale: en_GB, platform encoding: UTF-8 OS name: "mac os x", version:
"10.15.1", arch: "x86_64", family: "mac"
2019-11-29 13:05:06,759 [4279936]   INFO - pl.ProjectRootManagerComponent - project roots have changed 
2019-11-29 13:05:06,794 [4279971]   INFO - .diagnostic.PerformanceWatcher - Pushing properties took 4ms; general responsiveness: ok; EDT responsiveness: ok 
2019-11-29 13:05:06,815 [4279992]   INFO - .diagnostic.PerformanceWatcher - Indexable file iteration took 20ms; general responsiveness: ok; EDT responsiveness: ok 
2019-11-29 13:05:07,480 [4280657]   INFO -      #org.jetbrains.idea.maven - org.apache.maven.plugin.PluginResolutionException: Plugin org.codehaus.mojo:exec-maven-plugin:1.6.0 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.codehaus.mojo:exec-maven-plugin:jar:1.6.0 
java.lang.RuntimeException: org.apache.maven.plugin.PluginResolutionException: Plugin org.codehaus.mojo:exec-maven-plugin:1.6.0 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.codehaus.mojo:exec-maven-plugin:jar:1.6.0
	at org.apache.maven.plugin.internal.DefaultPluginDependenciesResolver.resolve(DefaultPluginDependenciesResolver.java:120)
	at org.jetbrains.idea.maven.server.Maven3XServerEmbedder.resolvePlugin(Maven3XServerEmbedder.java:1161)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:566)
	at java.rmi/sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:359)
	at java.rmi/sun.rmi.transport.Transport$1.run(Transport.java:200)
	at java.rmi/sun.rmi.transport.Transport$1.run(Transport.java:197)
	at java.base/java.security.AccessController.doPrivileged(Native Method)
	at java.rmi/sun.rmi.transport.Transport.serviceCall(Transport.java:196)
	at java.rmi/sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:562)
	at java.rmi/sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:796)
	at java.rmi/sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:677)
	at java.base/java.security.AccessController.doPrivileged(Native Method)
	at java.rmi/sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:676)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
	at java.base/java.lang.Thread.run(Thread.java:834)
Caused by: java.lang.RuntimeException: org.eclipse.aether.resolution.ArtifactDescriptorException: Failed to read artifact descriptor for org.codehaus.mojo:exec-maven-plugin:jar:1.6.0
	at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom(DefaultArtifactDescriptorReader.java:255)
	at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.readArtifactDescriptor(DefaultArtifactDescriptorReader.java:171)
	at org.eclipse.aether.internal.impl.DefaultRepositorySystem.readArtifactDescriptor(DefaultRepositorySystem.java:255)
	at org.apache.maven.plugin.internal.DefaultPluginDependenciesResolver.resolve(DefaultPluginDependenciesResolver.java:106)
	... 18 more
Caused by: java.lang.RuntimeException: org.eclipse.aether.resolution.ArtifactResolutionException: Failure to transfer org.codehaus.mojo:exec-maven-plugin:pom:1.6.0 from https://nexus.xxisp.yyyyyy.net/repository/public/ was cached in the local repository, resolution will not be reattempted until the update interval of nexus has elapsed or updates are forced. Original error: Could not transfer artifact org.codehaus.mojo:exec-maven-plugin:pom:1.6.0 from/to nexus (https://nexus.xxisp.yyyyyy.net/repository/public/): Connect to nexus.xxisp.yyyyyy.net:443 [nexus.xxisp.yyyyyy.net/81.135.143.77] failed: Operation timed out (Connection timed out)
	at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:424)
	at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:229)
	at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifact(DefaultArtifactResolver.java:207)
	at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom(DefaultArtifactDescriptorReader.java:240)
	... 21 more
Caused by: java.lang.RuntimeException: org.eclipse.aether.transfer.ArtifactTransferException: Failure to transfer org.codehaus.mojo:exec-maven-plugin:pom:1.6.0 from https://nexus.xxisp.yyyyyy.net/repository/public/ was cached in the local repository, resolution will not be reattempted until the update interval of nexus has elapsed or updates are forced. Original error: Could not transfer artifact org.codehaus.mojo:exec-maven-plugin:pom:1.6.0 from/to nexus (https://nexus.xxisp.yyyyyy.net/repository/public/): Connect to nexus.xxisp.yyyyyy.net:443 [nexus.xxisp.yyyyyy.net/81.135.143.77] failed: Operation timed out (Connection timed out)
	at org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.newException(DefaultUpdateCheckManager.java:225)
	at org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.checkArtifact(DefaultUpdateCheckManager.java:193)
	at org.eclipse.aether.internal.impl.DefaultArtifactResolver.gatherDownloads(DefaultArtifactResolver.java:559)
	at org.eclipse.aether.internal.impl.DefaultArtifactResolver.performDownloads(DefaultArtifactResolver.java:483)
	at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:401)
	... 24 more

有人知道如何调试并更好地修复它吗?

更新:我现在已经设法解决了这个问题。我想问题是,虽然在我升级的时候,我连接到了互联网,但我没有连接到我公司的VPN(因为那天我在家工作),这可能导致了对我公司的NEXUS回购的查找失败。后来,当我连接到VPN时,Maven由于某种原因无法重新同步插件。因此,这个问题与Intellij升级完全无关。我希望这种解决这些类型错误的技术可以帮助其他人。

共有1个答案

罗伟志
2023-03-14

这篇文章Gist/GitHub帮助我解决了这两个问题。

1/无法解析插件org.codehaus.mojo:exec-maven-plugin:1.6.0

我在。m2目录中找到了这个插件的条目,

/users/my-user/.m2/repository/org/apache/maven/plugins/maven-resources-plugin/3.1.0

我也删除了这个条目,然后从Intellij中进行了另一次Maven重新同步,这也起作用了。

 类似资料:
  • 我升级了我的AS,错误开始出现 我找了所有的地方,但我不能解决问题 这是我的构建。gradle(项目),脱机是未检查的,我做了无效和重启没有工作, 什么意思不能解决依赖?这是我在gradle(应用程序)中添加存储库时得到的结果

  • 我是Java EE和Maven的新手,所以我不确定需要哪些信息才能看到我犯了错误。 当我右键单击我的项目并进入Maven-->Reload project时,build选项卡打开,出现以下错误 当我悬停maven assembly插件时,IDE还告诉我 如果我需要任何进一步的信息,请告诉我。

  • 在将我的应用程序中的Vaadin从7.1.8升级到7.5.3之后,我遇到了一个奇怪的问题。 我的登录servlet无法处理任何请求,因为我认为Vaadin的安全密钥无效。 Vaadin现在使用elemental.json,当使用的第一次与应用程序交互时,我收到一个错误。 我浏览过SO和Vaadin论坛,我似乎是唯一有问题的人:( 任何帮助都将不胜感激。谢谢 这是堆栈 14:09:31,232 SE

  • 本文向大家介绍CentOS中升级Python版本的方法详解,包括了CentOS中升级Python版本的方法详解的使用技巧和注意事项,需要的朋友参考一下 CentOS升级Python2.6到Pythno2.7 最近在Linode上弄Python、出现ValueError: zero length field name in format这样的错误; 翻看文档之后发现只要升级Python到2.7以上版

  • 我在本地安装了gradle 4.7,下面是我的gradle.build,运行良好。gradle插件版本4.7在这一点上是成功的 当我运行gradle build时,它运行良好。 但是现在我需要将我的 SpringBootVersion 升级到 2.4.3(最新),我将文件中的第三行替换为以下内容: 但是我得到以下错误: 未能应用插件[id'org.springframework.boot']Spr

  • 我在Ubuntu18.04上使用ELasticsearch。当我尝试运行“./elasticsearch-setup-passwords”脚本时,它显示以下错误。 未来版本的Elasticsearch将需要Java 11;您的Java版本[/usr/lib/jvm/java-8-openjdk-amd64/jre]不符合此要求 但当我检查Jaa版本时,它显示的是Java 11号。 我把Java从8