eclipse 启动出错，could not read metadata

原创 已于 2022-11-23 01:19:39 修改 · 605 阅读 · 0 ·
CC 4.0 BY-SA版权
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
文章标签：

#eclipse

于 2022-04-13 23:02:56 首次发布
本文介绍了在Eclipse中遇到'Could not read metadata for...'错误的解决方案。通过点击文件-刷新，然后退出并重新打开Eclipse，可以解决意外版本号问题，从而恢复正常工作。

1.解决方案：

点击文件-刷新，然后点击退出，载重新打开eclipse；

2.遇到的问题

Could not read metadata for 
'D:\Eclipse\JavaProject\.metadata\.plugins\org.eclipse.core.resources\.root\.indexes\properties.index'. 
Unexpected version: 0.

Ericjim
关注
KETTLE 启动报错：Couldn‘t read the database cache
李指导的博客
04-11 718
在启动Kettle的时候报错: ERROR [di] null java.lang.RuntimeException: Unable to create the database cache: Couldn't read the database cacheUnable to read row metadata from input streamlinux定位到/root/.kettle目录；windows定位到：C:\Users\Administrator\.kettle 目录删除 db.cache-**
eclipse启动出现Could not read metadata for ……
weixin_33755847的博客
10-30 1441
Could not read metadata for …… E:\workspace\.metadata\.plugins\org.eclipse.core.resources\.projects\项目名 可以明显看出不能删除工作空间内项目的一些文件。该错误是在eclipse启动之后弹出的，可能还会伴有控制台输出一些错误。 我的做法很简单，由于此目录E:\workspace\....
使用eclipse时候出现Could not read metadata... 怎么解决?
tanghuan0827的博客
05-21 1297
找到这个文件properties.index并把它删了 重启eclipse 再clean一下工程 惊喜出现 转载地址：https://www.zhihu.com/question/36117612
Generating report An error occurred: Could not read metadata !
msdn_make的博客
12-12 4162
JMeter 生成html报告时报错如下： Generating report An error occurred: Could not read metadata ! 原因：生成报告需要从日志文件中获取数据，所以在查看结果树页面需要先指定生成的 .jtl 文件。然后再运行测试计划 运行测试计划后，能看到test.jtl中已经有保存的测试数据 生成html报告对话框中填写如下路径，Results file为刚运行测试计划生成的内容，user properties file为当前jmeter目
找不到metadata文件(Colud not read workspace metadata)
weixin_45444971的博客
03-11 1594
打开项目什么都没干就报这个错💢！！！clean项目和重启Android studio也不行。打开文件管理器发现确实没有这个文件。
Eclipse启动失败，提示查看.metadata文件夹下的.log文件
穷冬不见雪，正月已闻雷的博客
09-08 2620
Eclipse启动失败，提示查看.metadata文件夹下的.log文件 附上一些网上通用解决方法，方便以后查找： 尝试方法一：orkspace目录下的.metadata目录整个删除。结果：未成功。 尝试方法二：打开Eclipse安装目录下的configuration目录，删除org.eclipse.update和org.eclipse.osgi这两个文件夹。结果:成功启动。 ...
【Eclipse启动故障】：一步解决Windchill的启动噩梦
本文首先概述了Eclipse启动故障的一般情况，然后深入分析了故障诊断的理论基础，包括Eclipse的启动过程和常见故障点。接着，本文聚焦于Windchill环境下的启动问题，探讨了与Eclipse集成的机制、环境配置问
在构建期间出错。 在项目“acmr-ybms”中运行构建器“Maven Project Builder”时出错。 Could not calculate build plan: Plugin org.apache.maven.plugins:maven-war-plugin:2.2 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-war-plugin:jar:2.2 Plugin org.apache.maven.plugins:maven-war-plugin:2.2 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-war-plugin:jar:2.2 Could not calculate build plan: Plugin org.apache.maven.plugins:maven-war-plugin:2.2 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-war-plugin:jar:2.2 Plugin org.apache.maven.plugins:maven-war-plugin:2.2 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-war-plugin:jar:2.2 怎么解决
最新发布
11-22
- **IDE缓存**：重启IDE或删除IDE缓存目录（如Eclipse的`.metadata`）。 通过以上步骤，大多数类似问题可解决。如果问题依旧，建议查看[Maven官方文档](https://maven.apache.org/plugins/)或技术论坛获取插件特定...
STM32CubeIDE 启动失败时，通常会在工作目录下的 .metadata/.log 文件中生成日志信息
08-16
在 STM32CubeIDE 中，如果启动失败，通常会在工作空间目录下的 `.metadata/.log` 文件中记录相关的错误信息。这个日志文件对于诊断启动失败问题非常关键。以下是一些常见的启动失败原因以及如何查看日志文件的详细...
C:\Users\20182>mvn spring-boot:run -X Apache Maven 3.9.10 (5f519b97e944483d878815739f519b2eade0a91d) Maven home: D:\apache-maven-3.9.10-bin\apache-maven-3.9.10 Java version: 24.0.1, vendor: Oracle Corporation, runtime: D:\java Default locale: zh_CN, platform encoding: UTF-8 OS name: "windows 11", version: "10.0", arch: "amd64", family: "windows" WARNING: A terminally deprecated method in sun.misc.Unsafe has been called WARNING: sun.misc.Unsafe::staticFieldBase has been called by com.google.inject.internal.aop.HiddenClassDefiner (file:/D:/apache-maven-3.9.10-bin/apache-maven-3.9.10/lib/guice-5.1.0-classes.jar) WARNING: Please consider reporting this to the maintainers of class com.google.inject.internal.aop.HiddenClassDefiner WARNING: sun.misc.Unsafe::staticFieldBase will be removed in a future release [DEBUG] Created new class realm maven.api [DEBUG] Importing foreign packages into class realm maven.api [DEBUG] Imported: javax.annotation.* < plexus.core [DEBUG] Imported: javax.annotation.security.* < plexus.core [DEBUG] Imported: javax.inject.* < plexus.core [DEBUG] Imported: org.apache.maven.* < plexus.core [DEBUG] Imported: org.apache.maven.artifact < plexus.core [DEBUG] Imported: org.apache.maven.classrealm < plexus.core [DEBUG] Imported: org.apache.maven.cli < plexus.core [DEBUG] Imported: org.apache.maven.configuration < plexus.core [DEBUG] Imported: org.apache.maven.exception < plexus.core [DEBUG] Imported: org.apache.maven.execution < plexus.core [DEBUG] Imported: org.apache.maven.execution.scope < plexus.core [DEBUG] Imported: org.apache.maven.graph < plexus.core [DEBUG] Imported: org.apache.maven.lifecycle < plexus.core [DEBUG] Imported: org.apache.maven.model < plexus.core [DEBUG] Imported: org.apache.maven.monitor < plexus.core [DEBUG] Imported: org.apache.maven.plugin < plexus.core [DEBUG] Imported: org.apache.maven.profiles < plexus.core [DEBUG] Imported: org.apache.maven.project < plexus.core [DEBUG] Imported: org.apache.maven.reporting < plexus.core [DEBUG] Imported: org.apache.maven.repository < plexus.core [DEBUG] Imported: org.apache.maven.rtinfo < plexus.core [DEBUG] Imported: org.apache.maven.settings < plexus.core [DEBUG] Imported: org.apache.maven.toolchain < plexus.core [DEBUG] Imported: org.apache.maven.usability < plexus.core [DEBUG] Imported: org.apache.maven.wagon.* < plexus.core [DEBUG] Imported: org.apache.maven.wagon.authentication < plexus.core [DEBUG] Imported: org.apache.maven.wagon.authorization < plexus.core [DEBUG] Imported: org.apache.maven.wagon.events < plexus.core [DEBUG] Imported: org.apache.maven.wagon.observers < plexus.core [DEBUG] Imported: org.apache.maven.wagon.proxy < plexus.core [DEBUG] Imported: org.apache.maven.wagon.repository < plexus.core [DEBUG] Imported: org.apache.maven.wagon.resource < plexus.core [DEBUG] Imported: org.codehaus.classworlds < plexus.core [DEBUG] Imported: org.codehaus.plexus.* < plexus.core [DEBUG] Imported: org.codehaus.plexus.classworlds < plexus.core [DEBUG] Imported: org.codehaus.plexus.component < plexus.core [DEBUG] Imported: org.codehaus.plexus.configuration < plexus.core [DEBUG] Imported: org.codehaus.plexus.container < plexus.core [DEBUG] Imported: org.codehaus.plexus.context < plexus.core [DEBUG] Imported: org.codehaus.plexus.lifecycle < plexus.core [DEBUG] Imported: org.codehaus.plexus.logging < plexus.core [DEBUG] Imported: org.codehaus.plexus.personality < plexus.core [DEBUG] Imported: org.codehaus.plexus.util.xml.Xpp3Dom < plexus.core [DEBUG] Imported: org.codehaus.plexus.util.xml.pull.XmlPullParser < plexus.core [DEBUG] Imported: org.codehaus.plexus.util.xml.pull.XmlPullParserException < plexus.core [DEBUG] Imported: org.codehaus.plexus.util.xml.pull.XmlSerializer < plexus.core [DEBUG] Imported: org.eclipse.aether.* < plexus.core [DEBUG] Imported: org.eclipse.aether.artifact < plexus.core [DEBUG] Imported: org.eclipse.aether.collection < plexus.core [DEBUG] Imported: org.eclipse.aether.deployment < plexus.core [DEBUG] Imported: org.eclipse.aether.graph < plexus.core [DEBUG] Imported: org.eclipse.aether.impl < plexus.core [DEBUG] Imported: org.eclipse.aether.installation < plexus.core [DEBUG] Imported: org.eclipse.aether.internal.impl < plexus.core [DEBUG] Imported: org.eclipse.aether.metadata < plexus.core [DEBUG] Imported: org.eclipse.aether.repository < plexus.core [DEBUG] Imported: org.eclipse.aether.resolution < plexus.core [DEBUG] Imported: org.eclipse.aether.spi < plexus.core [DEBUG] Imported: org.eclipse.aether.transfer < plexus.core [DEBUG] Imported: org.eclipse.aether.util < plexus.core [DEBUG] Imported: org.eclipse.aether.version < plexus.core [DEBUG] Imported: org.fusesource.jansi.* < plexus.core [DEBUG] Imported: org.slf4j.* < plexus.core [DEBUG] Imported: org.slf4j.event.* < plexus.core [DEBUG] Imported: org.slf4j.helpers.* < plexus.core [DEBUG] Imported: org.slf4j.spi.* < plexus.core [DEBUG] Populating class realm maven.api [DEBUG] Created adapter factory; available factories [file-lock, rwlock-local, semaphore-local, noop]; available name mappers [discriminating, file-gav, file-hgav, file-static, gav, static] [INFO] Error stacktraces are turned on. [DEBUG] Message scheme: color [DEBUG] Message styles: debug info warning error success failure strong mojo project [DEBUG] Reading global settings from D:\apache-maven-3.9.10-bin\apache-maven-3.9.10\conf\settings.xml [DEBUG] Reading user settings from C:\Users\20182\.m2\settings.xml [WARNING] [WARNING] Some problems were encountered while building the effective settings [WARNING] expected START_TAG or END_TAG not TEXT (position: TEXT seen ...</activation>\n \u200b\n <p... @208:13) @ D:\apache-maven-3.9.10-bin\apache-maven-3.9.10\conf\settings.xml, line 208, column 13 [WARNING] [DEBUG] Reading global toolchains from D:\apache-maven-3.9.10-bin\apache-maven-3.9.10\conf\toolchains.xml [DEBUG] Reading user toolchains from C:\Users\20182\.m2\toolchains.xml [DEBUG] Using local repository at D:\apache-maven-3.9.10\repository [DEBUG] Using manager EnhancedLocalRepositoryManager with priority 10.0 for D:\apache-maven-3.9.10\repository [INFO] Scanning for projects... [DEBUG] Using mirror alimaven (http://maven.aliyun.com/nexus/content/groups/public/) for central (https://repo.maven.apache.org/maven2). [DEBUG] Extension realms for project org.apache.maven:standalone-pom:pom:1: (none) [DEBUG] Looking up lifecycle mappings for packaging pom from ClassRealm[plexus.core, parent: null] [DEBUG] Resolving plugin prefix spring-boot from [org.apache.maven.plugins, org.codehaus.mojo] [DEBUG] Creating adapter using nameMapper 'gav' and factory 'rwlock-local' [DEBUG] Could not find metadata org.apache.maven.plugins/maven-metadata.xml in local (D:\apache-maven-3.9.10\repository) [DEBUG] Skipped remote request for org.apache.maven.plugins/maven-metadata.xml, locally cached metadata up-to-date [DEBUG] Could not find metadata org.codehaus.mojo/maven-metadata.xml in local (D:\apache-maven-3.9.10\repository) [DEBUG] Skipped remote request for org.codehaus.mojo/maven-metadata.xml, locally cached metadata up-to-date [DEBUG] Could not find metadata org.apache.maven.plugins/maven-metadata.xml in local (D:\apache-maven-3.9.10\repository) [DEBUG] Could not find metadata org.codehaus.mojo/maven-metadata.xml in local (D:\apache-maven-3.9.10\repository) [DEBUG] Could not find metadata org.apache.maven.plugins/maven-metadata.xml in local (D:\apache-maven-3.9.10\repository) [DEBUG] Could not find metadata org.codehaus.mojo/maven-metadata.xml in local (D:\apache-maven-3.9.10\repository) [DEBUG] Using transporter HttpTransporter with priority 5.0 for http://maven.aliyun.com/nexus/content/groups/public/ [DEBUG] Using transporter HttpTransporter with priority 5.0 for http://maven.aliyun.com/nexus/content/groups/public/ [DEBUG] Using connector BasicRepositoryConnector with priority 0.0 for http://maven.aliyun.com/nexus/content/groups/public/ [DEBUG] Using connector BasicRepositoryConnector with priority 0.0 for http://maven.aliyun.com/nexus/content/groups/public/ Downloading from alimaven: http://maven.aliyun.com/nexus/content/groups/public/org/codehaus/mojo/maven-metadata.xml Downloading from alimaven: http://maven.aliyun.com/nexus/content/groups/public/org/apache/maven/plugins/maven-metadata.xml Downloaded from alimaven: http://maven.aliyun.com/nexus/content/groups/public/org/apache/maven/plugins/maven-metadata.xml (10 kB at 9.7 kB/s) Downloaded from alimaven: http://maven.aliyun.com/nexus/content/groups/public/org/codehaus/mojo/maven-metadata.xml (21 kB at 19 kB/s) [DEBUG] Writing tracking file 'D:\apache-maven-3.9.10\repository\org\apache\maven\plugins\resolver-status.properties' [DEBUG] Writing tracking file 'D:\apache-maven-3.9.10\repository\org\codehaus\mojo\resolver-status.properties' [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 1.655 s [INFO] Finished at: 2025-06-12T18:31:25+08:00 [INFO] ------------------------------------------------------------------------ [ERROR] No plugin found for prefix 'spring-boot' in the current project and in the plugin groups [org.apache.maven.plugins, org.codehaus.mojo] available from the repositories [local (D:\apache-maven-3.9.10\repository), alimaven (http://maven.aliyun.com/nexus/content/groups/public/)] -> [Help 1] org.apache.maven.plugin.prefix.NoPluginFoundForPrefixException: No plugin found for prefix 'spring-boot' in the current project and in the plugin groups [org.apache.maven.plugins, org.codehaus.mojo] available from the repositories [local (D:\apache-maven-3.9.10\repository), alimaven (http://maven.aliyun.com/nexus/content/groups/public/)] at org.apache.maven.plugin.prefix.internal.DefaultPluginPrefixResolver.resolve (DefaultPluginPrefixResolver.java:90) at org.apache.maven.lifecycle.internal.MojoDescriptorCreator.findPluginForPrefix (MojoDescriptorCreator.java:247) at org.apache.maven.lifecycle.internal.MojoDescriptorCreator.getMojoDescriptor (MojoDescriptorCreator.java:209) at org.apache.maven.lifecycle.internal.DefaultLifecycleTaskSegmentCalculator.calculateTaskSegments (DefaultLifecycleTaskSegmentCalculator.java:94) at org.apache.maven.lifecycle.internal.DefaultLifecycleTaskSegmentCalculator.calculateTaskSegments (DefaultLifecycleTaskSegmentCalculator.java:76) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:84) at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:261) at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:173) at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:101) at org.apache.maven.cli.MavenCli.execute (MavenCli.java:906) at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:283) at org.apache.maven.cli.MavenCli.main (MavenCli.java:206) at jdk.internal.reflect.DirectMethodHandleAccessor.invoke (DirectMethodHandleAccessor.java:104) at java.lang.reflect.Method.invoke (Method.java:565) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:255) at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:201) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:361) at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:314) [ERROR] [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/NoPluginFoundForPrefixException [DEBUG] Shutting down adapter factory; available factories [file-lock, rwlock-local, semaphore-local, noop]; available name mappers [discriminating, file-gav, file-hgav, file-static, gav, static] [DEBUG] Shutting down 'file-lock' factory [DEBUG] Shutting down 'rwlock-local' factory [DEBUG] Shutting down 'semaphore-local' factory [DEBUG] Shutting down 'noop' factory
06-13
### Maven构建失败问题：NoPluginFoundForPrefixException spring-boot plugin missing solution 当遇到 `NoPluginFoundForPrefixException` 错误时，通常是因为Maven无法找到指定的插件前缀（如 `spring-boot`）。...
eclipse错误之Could not write metadata for "xxx"
dianti5444的博客
06-09 809
Could not write metadata for '/test'. 这是由于删除一个项目时，没有同时在硬盘上删除该项目，而后又到硬盘文件系统中删除了该项目，才出现这问题的。 到eclipse工作空间workspace中找到\.metadata\.plugins\org.eclipse.core.resources\.projects 在其下面新建一个test再打开eclips...
解决Could not transfer metadata org.apache.maven.plugins:maven-archetype-plugin/..
weixin_51735258的博客
04-18 2万+
使用idea创建Springweb文件时， 报：Could not transfer metadata org.apache.maven.plugins:maven-archetype-plugin/maven-metadata.xml from/to alimaven (http://maven.aliyun.com/nexus/content/repositories/central/): Transfer failed for http://maven.aliyun.com/nexus/conten.
【解决】Android Gradle Sync 报错 Could not read workspace metadata
ZLGSPACE的博客
04-24 1691
针对“Android Gradle Sync 报错 Could not read workspace metadata”问题本文提供了对应的解决方法，可能并不是最优，但至少亲测可解决
【安卓开发】【Android Studio】项目构建失败提示【Could not read metadata.bin】解决方法
weixin_43031313的博客
01-02 2034
大概是提示gradle插件缓存目录（gradle/cache/xxx）下有一个metadata（元数据）的二进制文件无法读取。不需要去提示的缓存目录下查找这个metadata文件，只会让项目文件管理越来越乱。执行一次Build–>Clean Project即可。
Unable to read meta-data for class 快速解决启动异常
热门推荐
WUFUSHANLI的博客
04-21 2万+
Unable to read meta-data for class 快速解决启动异常1.问题还原2.重新审视3.解决问题正确代码注意：多个配置类必须用 ,\ 分开 最后一个不需要 1.问题还原 使用熔断异常在spring.factories配置熔断类路径 启动时报错如下： java.lang.IllegalStateException: Unable to read meta-data for class 2.重新审视 发现自定义spring.factories中类路径时多个configurti
Idea 无法引用类 找不到类 引用类报红 报错
wuyuanshun的博客
01-27 1331
Idea 无法引用类 找file->Invalidate Caches… 然后选择重启
The project was not built due to "Could not delete /项目名/target/classes/
weixin_30293135的博客
08-31 246
问题描述：编译项目的时候eclipse提示这个错误 解决方式： 百度翻译：由于“无法删除”，该项目未建立。 是文件删除不了，查了一下是别的软件吧这个项目的目录占用了， 导致没有权限操作classes下的文件，吧对应的软件关掉就好了 转载于:https://www.cnblogs.com/jinghu/p/7457004.html...
解决Could not write metadata for '/RemoteSystemsTempFiles'. D:\workspace\.metadata\.plugins\org.eclips
qq_36938933的博客
09-25 6515
问题描述eclipse启动后出现 解决方法找到project explorer view > customize view > Fileters > Uncheck “RSE internal projects” > OK; 删除 RemoteSystemsTempFiles; 问题解决请点个赞，希望大家多多 支持 ！如有问题请发私信
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值