redhat-developer / redhat-developer/vscode-java

!MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.core.resources".

未关闭
#3,306 3 条评论 1 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

bug
主要语言
TypeScript
星标
2.3k
派生
546
平均合并
20 小时 1 分钟
30 天内合并 PR
11

描述

!ENTRY org.eclipse.jdt.ls.core 4 0 2023-09-18 15:17:30.277
!MESSAGE Error updating com.microsoft.gradle.bs.importer
!STACK 0
java.lang.NullPointerException: Cannot invoke "org.eclipse.m2e.core.internal.MavenPluginActivator.getMavenMarkerManager()" because the return value of "org.eclipse.m2e.core.internal.MavenPluginActivator.getDefault()" is null
at org.eclipse.m2e.core.internal.builder.MavenBuilderImpl.processBuildResults(MavenBuilderImpl.java:343)
at org.eclipse.m2e.core.internal.builder.MavenBuilderImpl.build(MavenBuilderImpl.java:194)
at org.eclipse.m2e.core.project.configurator.AbstractLifecycleMapping.lambda$0(AbstractLifecycleMapping.java:114)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:394)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:275)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:214)
at org.eclipse.m2e.core.project.configurator.AbstractLifecycleMapping.configure(AbstractLifecycleMapping.java:114)
at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.lambda$6(ProjectConfigurationManager.java:504)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:394)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:275)
at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:498)
at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.lambda$4(ProjectConfigurationManager.java:426)
at java.base/java.util.Collection.removeIf(Unknown Source)
at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration0(ProjectConfigurationManager.java:414)
at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.lambda$3(ProjectConfigurationManager.java:340)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:394)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:275)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:214)
at org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1097)
at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:339)
at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:326)
at org.eclipse.jdt.ls.core.internal.managers.MavenBuildSupport.update(MavenBuildSupport.java:86)
at org.eclipse.jdt.ls.core.internal.managers.ProjectsManager$3.runInWorkspace(ProjectsManager.java:429)
at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:43)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)

!ENTRY org.eclipse.core.resources 4 2 2023-09-18 15:17:30.805
!MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.core.resources".
!STACK 0
org.eclipse.core.runtime.InvalidRegistryObjectException: Invalid registry object
at org.eclipse.core.internal.registry.RegistryObjectManager.basicGetObject(RegistryObjectManager.java:276)
at org.eclipse.core.internal.registry.RegistryObjectManager.getObject(RegistryObjectManager.java:266)
at org.eclipse.core.internal.registry.ConfigurationElementHandle.getConfigurationElement(ConfigurationElementHandle.java:29)
at org.eclipse.core.internal.registry.ConfigurationElementHandle.getName(ConfigurationElementHandle.java:111)
at org.eclipse.jdt.internal.launching.environments.AccessRuleParticipant.getDelegateClassName(AccessRuleParticipant.java:90)
at org.eclipse.jdt.internal.launching.environments.AccessRuleParticipant.hashCode(AccessRuleParticipant.java:113)
at java.base/java.util.HashMap.hash(Unknown Source)
at java.base/java.util.HashMap.put(Unknown Source)
at org.eclipse.jdt.internal.launching.environments.ExecutionEnvironment.collectRulesByParticipant(ExecutionEnvironment.java:389)
at org.eclipse.jdt.internal.launching.environments.ExecutionEnvironment.getAccessRules(ExecutionEnvironment.java:323)
at org.eclipse.jdt.internal.launching.JREContainer.computeClasspathEntries(JREContainer.java:299)
at org.eclipse.jdt.internal.launching.JREContainer.getClasspathEntries(JREContainer.java:272)
at org.eclipse.jdt.internal.launching.JREContainer.getClasspathEntries(JREContainer.java:390)
at org.eclipse.jdt.internal.core.JavaProject.resolveClasspath(JavaProject.java:3278)
at org.eclipse.jdt.internal.core.JavaProject.resolveClasspath(JavaProject.java:3436)
at org.eclipse.jdt.internal.core.ClasspathChange.generateDelta(ClasspathChange.java:247)
at org.eclipse.jdt.internal.core.DeltaProcessor.resourceChanged(DeltaProcessor.java:2129)
at org.eclipse.jdt.internal.core.DeltaProcessingState.resourceChanged(DeltaProcessingState.java:501)
at org.eclipse.core.internal.events.NotificationManager$1.run(NotificationManager.java:321)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:45)
at org.eclipse.core.internal.events.NotificationManager.notify(NotificationManager.java:311)
at org.eclipse.core.internal.events.NotificationManager.broadcastChanges(NotificationManager.java:174)
at org.eclipse.core.internal.resources.Workspace.broadcastPostChange(Workspace.java:458)
at org.eclipse.core.internal.resources.Workspace.endOperation(Workspace.java:1586)
at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:50)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)

!ENTRY org.eclipse.core.resources 4 2 2023-09-18 15:17:30.913
!MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.core.resources".
!STACK 0
org.eclipse.core.runtime.InvalidRegistryObjectException: Invalid registry object
at org.eclipse.core.internal.registry.RegistryObjectManager.basicGetObject(RegistryObjectManager.java:276)
at org.eclipse.core.internal.registry.RegistryObjectManager.getObject(RegistryObjectManager.java:266)
at org.eclipse.core.internal.registry.ConfigurationElementHandle.getConfigurationElement(ConfigurationElementHandle.java:29)
at org.eclipse.core.internal.registry.ConfigurationElementHandle.getName(ConfigurationElementHandle.java:111)
at org.eclipse.jdt.internal.launching.environments.AccessRuleParticipant.getDelegateClassName(AccessRuleParticipant.java:90)
at org.eclipse.jdt.internal.launching.environments.AccessRuleParticipant.hashCode(AccessRuleParticipant.java:113)
at java.base/java.util.HashMap.hash(Unknown Source)
at java.base/java.util.HashMap.put(Unknown Source)
at org.eclipse.jdt.internal.launching.environments.ExecutionEnvironment.collectRulesByParticipant(ExecutionEnvironment.java:389)
at org.eclipse.jdt.internal.launching.environments.ExecutionEnvironment.getAccessRules(ExecutionEnvironment.java:323)
at org.eclipse.jdt.internal.launching.JREContainer.computeClasspathEntries(JREContainer.java:299)
at org.eclipse.jdt.internal.launching.JREContainer.getClasspathEntries(JREContainer.java:272)
at org.eclipse.jdt.internal.launching.JREContainer.getClasspathEntries(JREContainer.java:390)
at org.eclipse.jdt.internal.core.JavaProject.resolveClasspath(JavaProject.java:3278)
at org.eclipse.jdt.internal.core.JavaProject.resolveClasspath(JavaProject.java:3436)
at org.eclipse.jdt.internal.core.JavaProject.getResolvedClasspath(JavaProject.java:2521)
at org.eclipse.jdt.internal.core.DeltaProcessingState.getRootInfos(DeltaProcessingState.java:335)
at org.eclipse.jdt.internal.core.DeltaProcessingState.initializeRoots(DeltaProcessingState.java:283)
at org.eclipse.jdt.internal.core.DeltaProcessor.resourceChanged(DeltaProcessor.java:2178)
at org.eclipse.jdt.internal.core.DeltaProcessingState.resourceChanged(DeltaProcessingState.java:501)
at org.eclipse.core.internal.events.NotificationManager$1.run(NotificationManager.java:321)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:45)
at org.eclipse.core.internal.events.NotificationManager.notify(NotificationManager.java:311)
at org.eclipse.core.internal.events.NotificationManager.broadcastChanges(NotificationManager.java:174)
at org.eclipse.core.internal.resources.Workspace.broadcastBuildEvent(Workspace.java:444)
at org.eclipse.core.internal.events.AutoBuildJob$AutoBuildOffJob.run(AutoBuildJob.java:376)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)

贡献指南

打开贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

调研方向

从报告的入口点 MavenBuilderImpl.processBuildResults 和 ProjectsManager.runInWorkspace 开始,然后跟踪生成 null activator 的 Maven 项目配置更新。同时检查 AccessRuleParticipant 和 ExecutionEnvironment 是否存在 InvalidRegistryObjectException。完成的标准是复现触发日志的工作流并消除这些错误;如果确定了相关的测试位置,则添加回归测试。

由索引模型根据 Issue 内容生成。

评估

技术栈
java
领域
tooling
Issue 类型
缺陷
难度
4/5
预计耗时
3-5 天
活跃度
停滞
描述清晰度
需要澄清
新手友好度
25/100

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。