Community
Participate
Working Groups
The following incident was reported via the automated error reporting: code: 4 plugin: org.eclipse.jdt.core_3.11.0.v20141209-1931 message: Exception while updating project references fingerprint: 6d63aec0 exception class: org.eclipse.core.internal.resources.ResourceException exception message: Could not set the project description for 'org.jboss.tools.hibernate4_3' because the project description file (.project) is out of sync with the file system. number of children: 1 org.eclipse.core.internal.resources.ResourceException: Could not set the project description for 'org.jboss.tools.hibernate4_3' because the project description file (.project) is out of sync with the file system. at org.eclipse.core.internal.resources.Project.setDescription(Project.java:1365) at org.eclipse.jdt.internal.core.ProjectReferenceChange$1.run(ProjectReferenceChange.java:108) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2313) at org.eclipse.jdt.internal.core.ProjectReferenceChange.updateProjectReferencesIfNecessary(ProjectReferenceChange.java:111) at org.eclipse.jdt.internal.core.DeltaProcessor.resourceChanged(DeltaProcessor.java:2152) at org.eclipse.jdt.internal.core.DeltaProcessingState.resourceChanged(DeltaProcessingState.java:477) at org.eclipse.core.internal.events.NotificationManager$1.run(NotificationManager.java:295) 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:151) at org.eclipse.core.internal.resources.Workspace.broadcastBuildEvent(Workspace.java:362) at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:140) at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) --- code: 274 plugin: org.eclipse.core.resources_3.9.100.v20141128-1217 message: Could not set the project description for 'org.jboss.tools.hibernate4_3' because the project description file (.project) is out of sync with the file system. fingerprint: 00000000 number of children: 0 General Information: reported-by: Alexey Kazakov anonymous-id: 9689f266-628d-3665-981d-c9efffc003c3 eclipse-build-id: 4.5.0.I20141210-2000 eclipse-product: org.eclipse.epp.package.committers.product operating system: Linux 3.16.0 (x86_64) - gtk jre-version: 1.7.0_55-b13 The following plug-ins were present on the execution stack (*): 1. org.eclipse.core.jobs_3.7.0.v20141128-1953 2. org.eclipse.core.resources_3.9.100.v20141128-1217 3. org.eclipse.core.runtime_3.10.0.v20140724-1132 4. org.eclipse.jdt.core_3.11.0.v20141209-1931 5. org.eclipse.jdt_3.11.0.v20141210-2000 Please note that: * Messages, stacktraces, and nested status objects may be shortened. * Bug fields like status, resolution, and whiteboard are sent back to reporters. * The list of present bundles and their respective versions was calculated by package naming heuristics. This may or may not reflect reality. Other Resources: * Report: https://dev.eclipse.org/recommenders/committers/confess/#/problems/54c4f75fbee810030da0d8ca * Manual: https://dev.eclipse.org/recommenders/community/confess/#/guide Thank you for your assistance. Your friendly error-reports-inbox.
Hmm.. I doubt JDT has anything to do with this. But it will be good to get more information on this.
I had similar issue in Windows merely creating a JSF project when using a UNC path to a Synology NAS SMB share. I used a C: workspace and it worked fine. I'll try to create that bug report, but thought it might be useful to know here.
I encountered this bug when I did the following: - I had the project open in eclipse. - From the command line I rm -rf the entire project. - I then re-cloned the project using the command line. - I then switched back to eclipse and deleted the open projects.
(In reply to Sean Smitz from comment #3) > I encountered this bug when I did the following: > - I had the project open in eclipse. > - From the command line I rm -rf the entire project. > - I then re-cloned the project using the command line. > - I then switched back to eclipse and deleted the open projects. What happens when you try refreshing the package explorer before that?
I had this issue when importing an existing (plugin)project into the workspace.
I had this issue when switching branches in GIT with eclipse open: - While some projects existed in one branch and not in the other - While the first project was a maven project and the other a normal java project
Might happen when m2e updates the .project file after changes in the POM since I see the error close to the one in the original report in my error log: Java Model Exception: Core Exception [code 274] Could not set the project description for 'fundfinder-deutschebank' because the project description file (.project) is out of sync with the file system. at org.eclipse.jdt.internal.core.ProjectReferenceChange.updateProjectReferencesIfNecessary(ProjectReferenceChange.java:114) at org.eclipse.jdt.internal.core.ChangeClasspathOperation.classpathChanged(ChangeClasspathOperation.java:59) at org.eclipse.jdt.internal.core.SetContainerOperation.executeOperation(SetContainerOperation.java:110) at org.eclipse.jdt.internal.core.JavaModelOperation.run(JavaModelOperation.java:729) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2241) at org.eclipse.jdt.internal.core.JavaModelOperation.runOperation(JavaModelOperation.java:794) at org.eclipse.jdt.core.JavaCore.setClasspathContainer(JavaCore.java:5479) at org.eclipse.m2e.jdt.internal.BuildPathManager.updateClasspath(BuildPathManager.java:193) at org.eclipse.m2e.jdt.internal.BuildPathManager.mavenProjectChanged(BuildPathManager.java:180) at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.notifyProjectChangeListeners(ProjectRegistryManager.java:783) at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.applyMutableProjectRegistry(ProjectRegistryManager.java:919) at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.refresh(ProjectRegistryManager.java:299) at org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod.getProjectFacade(MavenBuilder.java:154) at org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod$1.call(MavenBuilder.java:89) at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176) at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:151) at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:99) at org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod.execute(MavenBuilder.java:86) at org.eclipse.m2e.core.internal.builder.MavenBuilder.build(MavenBuilder.java:200) at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:734) ...
This happens when the eclipse project files are re-generated by an external build tool. In our context, it isbecause a gradle build is in charge of generating classpath files. Hope it helps ;-)
Having this issue when switching branches (doing mostly via CLI). Refresh of the project does not seem to help. Closing and reopeninning the corresponding project helped.
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.
