Community
Participate
Working Groups
While using M6 I am getting numerous error reading manifest console messages, some duplicates, some from closed files. The errors occur after launching a nested Eclipse and then doing a clean to provoke a getActiveBundles(). Debugging I see that .metadata\.plugins\org.eclipse.pde.core\New_configuration (1)\org.eclipse.equinox.simpleconfigurator\bundles.info is an important file. When I look at the start of it I see: #encoding=UTF-8 #version=1 Activity,1.0.0.qualifier,file:/E:/Development/Chital/Workspace/Activity/,4,false BugEMFInstances,0.1.0.qualifier,file:/E:/Development/Chital/Workspace/BugEMFInstances/,4,false _QVTd_QVTrCompilerTests__testQVTrCompiler_ATL2QVTr_CG,1.0.0,file:/E:/Development/Chital/Workspace/_QVTd_QVTrCompilerTests__testQVTrCompiler_ATL2QVTr_CG/,4,false _QVTd_QVTrCompilerTests__testQVTrCompiler_ATL2QVTr_CG,1.0.0,file:/E:/Development/Chital/Workspace/_QVTd_QVTrCompilerTests__testQVTrCompiler_ATL2QVTr_CG/,4,false _QVTd_QVTrCompilerTests__testQVTrCompiler_Ecore2Pivot_CG,1.0.0,file:/E:/Development/Chital/Workspace/_QVTd_QVTrCompilerTests__testQVTrCompiler_Ecore2Pivot_CG/,4,false _QVTd_QVTrCompilerTests__testQVTrCompiler_Families2Persons_CG,1.0.0,file:/E:/Development/Chital/Workspace/_QVTd_QVTrCompilerTests__testQVTrCompiler_Families2Persons_CG/,4,false _QVTd_QVTrCompilerTests__testQVTrCompiler_Forward2Reverse_CG,1.0.0,file:/E:/Development/Chital/Workspace/_QVTd_QVTrCompilerTests__testQVTrCompiler_Forward2Reverse_CG/,4,false _QVTd_QVTrCompilerTests__testQVTrCompiler_Forward2Reverse_CG,1.0.0,file:/E:/Development/Chital/Workspace/_QVTd_QVTrCompilerTests__testQVTrCompiler_Forward2Reverse_CG/,4,false _QVTd_QVTrCompilerTests__testQVTrCompiler_Forward2Reverse_CG,1.0.0,file:/E:/Development/Chital/Workspace/_QVTd_QVTrCompilerTests__testQVTrCompiler_Forward2Reverse_CG/,4,false _QVTd_QVTrCompilerTests__testQVTrCompiler_Forward2Reverse_CG,1.0.0,file:/E:/Development/Chital/Workspace/_QVTd_QVTrCompilerTests__testQVTrCompiler_Forward2Reverse_CG/,4,false _QVTd_QVTrCompilerTests__testQVTrCompiler_Forward2Reverse_CG,1.0.0,file:/E:/Development/Chital/Workspace/_QVTd_QVTrCompilerTests__testQVTrCompiler_Forward2Reverse_CG/,4,false _QVTd_QVTrCompilerTests__testQVTrCompiler_Forward2Reverse_CG,1.0.0,file:/E:/Development/Chital/Workspace/_QVTd_QVTrCompilerTests__testQVTrCompiler_Forward2Reverse_CG/,4,false _QVTd_QVTrCompilerTests__testQVTrCompiler_Forward2Reverse_CG,1.0.0,file:/E:/Development/Chital/Workspace/_QVTd_QVTrCompilerTests__testQVTrCompiler_Forward2Reverse_CG/,4,false _QVTd_QVTrCompilerTests__testQVTrCompiler_HierarchicalStateMachine2FlatStateMachine_CG,1.0.0,file:/E:/Development/Chital/Workspace/_QVTd_QVTrCompilerTests__testQVTrCompiler_HierarchicalStateMachine2FlatStateMachine_CG/,4,false _QVTd_QVTrCompilerTests__testQVTrCompiler_Iterated2Iterated_CG,1.0.0,file:/E:/Development/Chital/Workspace/_QVTd_QVTrCompilerTests__testQVTrCompiler_Iterated2Iterated_CG/,4,false _QVTd_QVTrCompilerTests__testQVTrCompiler_MiToSiSimple_CG,1.0.0,file:/E:/Development/Chital/Workspace/_QVTd_QVTrCompilerTests__testQVTrCompiler_MiToSiSimple_CG/,4,false _QVTd_QVTrCompilerTests__testQVTrCompiler_SeqToStm_CG,1.0.0,file:/E:/Development/Chital/Workspace/_QVTd_QVTrCompilerTests__testQVTrCompiler_SeqToStm_CG/,4,false Note the duplicate entries which along with some other entries correspond to closed projects. Surely they should have been pruned so that no manifest read errors result?
What you provided doesn't look like log entries. Can you provide steps to reproduce?
It doesn't seem to be new to M6. I have an M5 machine that has similar entries. The log is just full of messages such as the log below from a closed project. I suspect the problem is how did the bad entries get into org.eclipse.equinox.simpleconfigurator\bundles.info. The entries correspond to auto-created pseudo-project folders to workaround Tycho's understandable inability to create temporary files in packaged JARs unlike PDE's ability to create temporary files in unpackaged bin folders. The pseudo-projects enable Tycho tests to auto-generate and test project content. Occasionally for debugging, the pseudo-project can be imported into the workspace as a real project, which thereafter is sometimes closed, sometimes open, to suit debugging utility. (Running the Tycho-test deletes all files in the pseudo-project including the .project file.) !ENTRY org.eclipse.pde.core 4 0 2018-03-21 10:29:09.698 !MESSAGE Error reading manifest for E:\Development\Chital\Workspace\_QVTd_UMLXCompilerTests__testUMLXCompiler_Forward2Reverse_CG2 !STACK 1 org.eclipse.core.runtime.CoreException: Error reading manifest for E:\Development\Chital\Workspace\_QVTd_UMLXCompilerTests__testUMLXCompiler_Forward2Reverse_CG2 at org.eclipse.pde.internal.core.util.ManifestUtils.loadManifest(ManifestUtils.java:117) at org.eclipse.pde.internal.core.MinimalState.addBundle(MinimalState.java:105) at org.eclipse.pde.internal.core.MinimalState.addBundle(MinimalState.java:71) at org.eclipse.pde.internal.core.PluginModelManager.addWorkspaceBundleToState(PluginModelManager.java:709) at org.eclipse.pde.internal.core.PluginModelManager.addWorkspaceBundleToState(PluginModelManager.java:687) at org.eclipse.pde.internal.core.PluginModelManager.handleAdd(PluginModelManager.java:847) at org.eclipse.pde.internal.core.PluginModelManager.handleChange(PluginModelManager.java:908) at org.eclipse.pde.internal.core.PluginModelManager.modelsChanged(PluginModelManager.java:234) at org.eclipse.pde.internal.core.AbstractModelManager.fireModelProviderEvent(AbstractModelManager.java:34) at org.eclipse.pde.internal.core.WorkspaceModelManager.createAndFireEvent(WorkspaceModelManager.java:259) at org.eclipse.pde.internal.core.WorkspacePluginModelManager.createAndFireEvent(WorkspacePluginModelManager.java:482) at org.eclipse.pde.internal.core.WorkspaceModelManager.processModelChanges(WorkspaceModelManager.java:231) at org.eclipse.pde.internal.core.WorkspaceModelManager.processModelChanges(WorkspaceModelManager.java:193) at org.eclipse.pde.internal.core.WorkspacePluginModelManager.processModelChanges(WorkspacePluginModelManager.java:471) at org.eclipse.pde.internal.core.WorkspaceModelManager.resourceChanged(WorkspaceModelManager.java:113) at org.eclipse.jdt.internal.core.DeltaProcessingState$1.run(DeltaProcessingState.java:471) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.jdt.internal.core.DeltaProcessingState.resourceChanged(DeltaProcessingState.java:464) at org.eclipse.core.internal.events.NotificationManager$1.run(NotificationManager.java:297) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.NotificationManager.notify(NotificationManager.java:287) at org.eclipse.core.internal.events.NotificationManager.broadcastChanges(NotificationManager.java:150) at org.eclipse.core.internal.resources.Workspace.broadcastPostChange(Workspace.java:376) at org.eclipse.core.internal.resources.Workspace.checkpoint(Workspace.java:562) at org.eclipse.ltk.core.refactoring.PerformChangeOperation$1.run(PerformChangeOperation.java:262) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2289) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2316) at org.eclipse.ltk.core.refactoring.PerformChangeOperation.executeChange(PerformChangeOperation.java:305) at org.eclipse.ltk.internal.ui.refactoring.UIPerformChangeOperation.executeChange(UIPerformChangeOperation.java:96) at org.eclipse.ltk.core.refactoring.PerformChangeOperation.run(PerformChangeOperation.java:216) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2289) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2316) at org.eclipse.ltk.internal.ui.refactoring.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:86) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119) !SUBENTRY 1 org.eclipse.pde.core 4 204 2018-03-21 10:29:09.698 !MESSAGE Error reading manifest for E:\Development\Chital\Workspace\_QVTd_UMLXCompilerTests__testUMLXCompiler_Forward2Reverse_CG2
Created attachment 273247 [details] Repro project The problem also occurs for a JUnit Plugin launch, but seems more disciplined; closed projects are ignored. The attached project provokes two "Error reading manifest" console entries with an independent JUnit plugin test that accesses bundles. The project has an almost empty .project and plugin.xml, but no MANIFEST.MF. It seems to be the 'missing' MANIFEST.MF that causes one form of the failure. !MESSAGE The current target platform contains errors, open Window > Preferences > Plug-in Development > Target Platform for details. !STACK 1 org.eclipse.core.runtime.CoreException: Problems occurred getting the plug-ins in this container at org.eclipse.pde.internal.core.PluginModelManager.getExternalBundles(PluginModelManager.java:629) at org.eclipse.pde.internal.core.PluginModelManager.initializeTable(PluginModelManager.java:539) at org.eclipse.pde.internal.core.PluginModelManager.targetReloaded(PluginModelManager.java:471) at org.eclipse.pde.internal.core.RequiredPluginsInitializer$1.run(RequiredPluginsInitializer.java:31) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:60) Contains: Error reading manifest for E:\Development\Rusa\Workspace\_QVTd_QVTrCompilerTests__testQVTrCompiler_Families2Persons_CG !SUBENTRY 1 org.eclipse.pde.core 4 0 2018-03-21 16:46:05.967 !MESSAGE Problems occurred getting the plug-ins in this container !SUBENTRY 2 org.eclipse.pde.core 4 204 2018-03-21 16:46:05.968 !MESSAGE Error reading manifest for E:\Development\Rusa\Workspace\_QVTd_QVTrCompilerTests__testQVTrCompiler_Families2Persons_CG !ENTRY org.eclipse.pde.core 4 204 2018-03-21 16:46:05.970 !MESSAGE Error reading manifest for E:\Development\Rusa\Workspace\_QVTd_QVTrCompilerTests__testQVTrCompiler_Families2Persons_CG The target platform is the "Running Platform (Active)" for which Window > Preferences > Plug-in Development > Target Platform show no problems.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
IIRC there have been some improvements to non-use of closed projects which may well have fixed this bug. I don't recall seeing it recently.
Please reopen if the problem still persists.
