Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 313460

Summary:	Rename a project in the PE, Error messages in log "Problems occurred when invoking code from plug-in "org.eclipse.core.resources"
Product:	[Tools] CDT	Reporter:	Anthony Hunter <ahunter.eclipse>
Component:	cdt-core	Assignee:	Project Inbox <cdt-core-inbox>
Status:	RESOLVED DUPLICATE	QA Contact:	Doug Schaefer <cdtdoug>
Severity:	normal
Priority:	P3	CC:	jamesblackburn+eclipse
Version:	7.0
Target Milestone:	---
Hardware:	PC
OS:	Linux
Whiteboard:

Description Anthony Hunter

2010-05-18 23:52:01 EDT

Using M7 builds:
Select a project in the project explorer, right click and select Rename, give the project a new name and save.
When you click OK, error messages appear in the Error log view.

!ENTRY org.eclipse.core.resources 4 2 2010-03-30 16:59:57.712
!MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.core.resources".
!STACK 0
java.lang.NullPointerException
	at org.eclipse.cdt.internal.core.settings.model.CProjectDescriptionManager.projectMove(Unknown Source)
	at org.eclipse.cdt.internal.core.settings.model.ResourceChangeHandler$RcMoveHandler.handleResourceMove(Unknown Source)
	at org.eclipse.cdt.core.settings.model.util.ResourceChangeHandlerBase$DeltaVisitor.checkInitHandleResourceMove(Unknown Source)
	at org.eclipse.cdt.core.settings.model.util.ResourceChangeHandlerBase$DeltaVisitor.visit(Unknown Source)
	at org.eclipse.core.internal.events.ResourceDelta.accept(Unknown Source)
	at org.eclipse.core.internal.events.ResourceDelta.accept(Unknown Source)
	at org.eclipse.core.internal.events.ResourceDelta.accept(Unknown Source)
	at org.eclipse.cdt.core.settings.model.util.ResourceChangeHandlerBase.doHandleResourceMove(Unknown Source)
	at org.eclipse.cdt.internal.core.settings.model.ResourceChangeHandler.doHandleResourceMove(Unknown Source)
	at org.eclipse.cdt.core.settings.model.util.ResourceChangeHandlerBase.resourceChanged(Unknown Source)
	at org.eclipse.core.internal.events.NotificationManager$2.run(Unknown Source)
	at org.eclipse.core.runtime.SafeRunner.run(Unknown Source)
	at org.eclipse.core.internal.events.NotificationManager.notify(Unknown Source)
	at org.eclipse.core.internal.events.NotificationManager.broadcastChanges(Unknown Source)
	at org.eclipse.core.internal.resources.Workspace.broadcastPostChange(Unknown Source)
	at org.eclipse.core.internal.resources.Workspace.checkpoint(Unknown Source)
	at org.eclipse.ltk.core.refactoring.PerformChangeOperation$1.run(Unknown Source)
	at org.eclipse.core.internal.resources.Workspace.run(Unknown Source)
	at org.eclipse.ltk.core.refactoring.PerformChangeOperation.executeChange(Unknown Source)
	at org.eclipse.ltk.internal.ui.refactoring.UIPerformChangeOperation.executeChange(Unknown Source)
	at org.eclipse.ltk.core.refactoring.PerformChangeOperation.run(Unknown Source)
	at org.eclipse.core.internal.resources.Workspace.run(Unknown Source)
	at org.eclipse.ltk.internal.ui.refactoring.WorkbenchRunnableAdapter.run(Unknown Source)
	at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(Unknown Source)

Comment 1 James Blackburn

2010-05-19 04:06:13 EDT

I think this is caused by Bug 286384.

It was fixed in 2010-03-31 so must have missed the build you're using. BTW for future do try to report issues with source.

*** This bug has been marked as a duplicate of bug 286384 ***