redhat-developer / redhat-developer/vscode-java
!MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.core.resources".
Dieses Issue hat noch niemand übernommen.
- Vorherrschende Sprache
- TypeScript
- Sterne
- 2.3k
- Forks
- 546
- Ø Merge
- 20 Std. 1 Min.
- Gemergte PRs (30 T.)
- 11
Beschreibung
!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)
Beitragsleitfaden
Erste Schritte
- Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
- Forke das Repository und arbeite in einem Branch.
- Öffne einen Pull Request, der die Issue-Nummer nennt.
Rechercherichtung
Beginne mit den gemeldeten Einstiegspunkten MavenBuilderImpl.processBuildResults und ProjectsManager.runInWorkspace und verfolge dann die Aktualisierung der Maven-Projektkonfiguration, die den null-Aktivator erzeugt. Untersuche außerdem AccessRuleParticipant und ExecutionEnvironment im Hinblick auf die InvalidRegistryObjectException. Als abgeschlossen gilt die Reproduktion des Workflows, der den Log-Eintrag auslöst, und die Beseitigung dieser Fehler, mit einem Regressionstest, falls der relevante Testort identifiziert wird.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- java
- Bereich
- tooling
- Issue-Typ
- Bug
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Aktivitätsstatus
- Veraltet
- Klarheit
- Muss geklärt werden
- Anfängerfreundlichkeit
- 25/100