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

Bug 362947

Summary:	Renaming project can temporarily corrupt project settings
Product:	z_Archived	Reporter:	Justin Spadea <jspadea>
Component:	EDT	Assignee:	pf yu <pfyu>
Status:	NEW ---	QA Contact:
Severity:	normal
Priority:	P3	CC:	chenzhh, svihovec
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Linux
Whiteboard:

Description Justin Spadea

2011-11-04 15:51:06 EDT

If I create a project, sometimes when I rename it, it "loses" its EDT Compiler settings. The files in .settings/ look correct, but if you go to the EGL Compiler property page, it says it's no longer overriding workspace defaults.

Restarting the workspace causes the files on disk to be re-read, so it's just what's in memory that's wrong.

This doesn't always happen, but if I rename a project a few times, it eventually happens. e.g. create a project 'refactorProj' then rename it to 'refactorProj2' then back to 'refactorProj', back and forth between the two.

When this happens, the value for the default DD file does not get updated. The setting is .settings/org.eclipse.edt.ide.core.prefs, key=DefaultDeploymentDescriptorPath/<project>

Furthermore, when it *doesn't* fail, the value of the default DD is updated incorrectly. It changes both the project name AND the DD file name:
DefaultDeploymentDescriptorPath/<project>=/refactorProj2/EGLSource/refactorProj2.egldd

Renaming the project portion of the path is correct, but the file is still called refactorProj.egldd (no '2'), it was not changed when the project was renamed.

Comment 1 Brian Svihovec

2011-11-14 16:25:01 EST

We are willing to let an investigation continue for this defect, but any changes should be discussed before they are committed.  If this defect can be deferred, it should be marked as "Future".

Comment 2 Lisa Lasher

2011-11-16 16:29:13 EST

deferred

Comment 3 Brian Svihovec

2011-12-16 11:04:28 EST

We should determine what is going on here and resolve any issues we find.

Comment 4 Huo Zhen Zhong

2012-03-30 04:24:06 EDT

There is no chance to fix it in 0.8, will look at it in the refactor support