Download
Getting Started
Members
Projects
Community
Marketplace
Events
Planet Eclipse
Newsletter
Videos
Participate
Report a Bug
Forums
Mailing Lists
Wiki
IRC
How to Contribute
Working Groups
Automotive
Internet of Things
LocationTech
Long-Term Support
PolarSys
Science
OpenMDM
More
Community
Marketplace
Events
Planet Eclipse
Newsletter
Videos
Participate
Report a Bug
Forums
Mailing Lists
Wiki
IRC
How to Contribute
Working Groups
Automotive
Internet of Things
LocationTech
Long-Term Support
PolarSys
Science
OpenMDM
Toggle navigation
Bugzilla – Attachment 159764 Details for
Bug 108066
[prefs] core.prefs settings file causing repeating version conflicts
Home
|
New
|
Browse
|
Search
|
[?]
|
Reports
|
Requests
|
Help
|
Log In
[x]
|
Terms of Use
|
Copyright Agent
Relevant stack-traces when reproducing the issue
bug108066.txt (text/plain), 4.94 KB, created by
Markus Schorn
on 2010-02-22 06:57:22 EST
(
hide
)
Description:
Relevant stack-traces when reproducing the issue
Filename:
MIME Type:
Creator:
Markus Schorn
Created:
2010-02-22 06:57:22 EST
Size:
4.94 KB
patch
obsolete
>The issue can be reproduced in the debugger (using 3.6M4): > >1) Set a breakpoint at the beginning of the method RefreshJob.runInWorkspace(...) >2) Import a java-project with a file '.settings/org.eclipse.jdt.core.prefs' >--> The java indexer is notified about the new project and accesses the > project preferences. The preference node is created, an attempt to load > them from file is made, however the file does not yet exist, so the node > remains to be empty. > >3) After that let the refresh job continue >--> When the file '.settings/org.eclipse.jdt.core.prefs' is refreshed, the > existing empty project preference node is updated and marked as dirty. > It is not yet flushed to disk at this point (because flag isLoading is set). > > Note: If the project preference node does not yet exist at this point, > it is created and loaded and updated. Then the update does not actually > change anything, so the node is not set dirty and we are fine) > >4) Any operation that flushes the preference tree now causes the dirty node > to be flushed to disk. E.g. a preference import will trigger that. > > > >JDT Indexer is triggered: >========================= >IndexAllProject.<init>(IProject, IndexManager) line: 41 >IndexManager.indexAll(IProject) line: 459 >DeltaProcessor.updateIndex(Openable, IResourceDelta) line: 2479 >DeltaProcessor.updateCurrentDeltaAndIndex(IResourceDelta, int, DeltaProcessor$RootInfo) line: 2354 >DeltaProcessor.traverseDelta(IResourceDelta, int, DeltaProcessor$RootInfo, DeltaProcessor$OutputsInfo) line: 2082 >DeltaProcessor.processResourceDelta(IResourceDelta) line: 1781 >DeltaProcessor.resourceChanged(IResourceChangeEvent) line: 1943 >DeltaProcessingState.resourceChanged(IResourceChangeEvent) line: 470 >NotificationManager$2.run() line: 291 >SafeRunner.run(ISafeRunnable) line: 42 >NotificationManager.notify(ResourceChangeListenerList$ListenerEntry[], IResourceChangeEvent, boolean) line: 285 >NotificationManager.broadcastChanges(ElementTree, ResourceChangeEvent, boolean) line: 149 >Workspace.broadcastPostChange() line: 325 >Workspace.endOperation(ISchedulingRule, boolean, IProgressMonitor) line: 1063 >Workspace.run(IWorkspaceRunnable, ISchedulingRule, int, IProgressMonitor) line: 1866 >WizardProjectsImportPage$16(WorkspaceModifyOperation).run(IProgressMonitor) line: 118 >ModalContext$ModalContextThread.run() line: 121 > > >RefreshJob stops at breakpoint: >=============================== >RefreshJob.runInWorkspace(IProgressMonitor) line: 158 >RefreshJob(InternalWorkspaceJob).run(IProgressMonitor) line: 38 >Worker.run() line: 55 > > >Project Preferences are created without loading: >===================================================================== >ProjectPreferences.load() line: 485 >ProjectPreferences(EclipsePreferences).create(EclipsePreferences, String, Object) line: 307 >ProjectPreferences(EclipsePreferences).internalNode(String, boolean, Object) line: 543 >ProjectPreferences(EclipsePreferences).node(String) line: 669 >ProjectScope.getNode(String) line: 67 >JavaProject.getEclipsePreferences() line: 1410 >JavaProject.getOptions(boolean) line: 1603 >IndexManager.getSourceElementParser(IJavaProject, ISourceElementRequestor) line: 182 >IndexAllProject.execute(IProgressMonitor) line: 203 > > >Project Preferences marked as dirty: >===================================== >ProjectPreferences(EclipsePreferences).put(String, String) line: 768 >PreferencesService$1.visit(IEclipsePreferences) line: 176 >ExportedPreferences(EclipsePreferences).accept(IPreferenceNodeVisitor) line: 105 >PreferencesService.applyPreferences(IExportedPreferences) line: 197 >ProjectPreferences.read(ProjectPreferences, IFile) line: 263 >ProjectPreferences.updatePreferences(IFile) line: 331 >File.updateMetadataFiles() line: 410 >RefreshLocalAliasVisitor(RefreshLocalVisitor).visit(UnifiedTreeNode) line: 294 >UnifiedTree.accept(IUnifiedTreeVisitor, int) line: 108 >FileSystemResourceManager.refreshResource(IResource, int, boolean, IProgressMonitor) line: 790 >FileSystemResourceManager.refresh(IResource, int, boolean, IProgressMonitor) line: 774 >Project(Resource).refreshLocal(int, IProgressMonitor) line: 1783 >RefreshJob.runInWorkspace(IProgressMonitor) line: 166 >RefreshJob(InternalWorkspaceJob).run(IProgressMonitor) line: 38 > > >Project Preferences written to disk: >===================================== >ProjectPreferences.save() line: 622 >ProjectPreferences(EclipsePreferences).flush() line: 352 >ProjectPreferences.flush() line: 420 >ProjectPreferences(EclipsePreferences).flush() line: 334 >ProjectPreferences.flush() line: 420 >ProjectPreferences(EclipsePreferences).flush() line: 334 >ProjectPreferences.flush() line: 420 >RootPreferences.flush() line: 39 >PreferencesService.applyPreferences(IEclipsePreferences, IPreferenceFilter[]) line: 96 >WizardPreferencesImportPage1.transfer(IPreferenceFilter[]) line: 185 >WizardPreferencesImportPage1(WizardPreferencesPage).finish() line: 619 >PreferencesImportWizard.performFinish() line: 88 >
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Raw
Actions:
View
Attachments on
bug 108066
: 159764 |
159920
|
159954