Community
Participate
Working Groups
the .project file of any EDT project contains two entries for eglnature with different case. <natures> <nature>org.eclipse.jdt.core.javanature</nature> <nature>org.eclipse.edt.ide.core.EGLNature</nature> <nature>org.eclipse.edt.ide.core.eglnature</nature> </natures>
Setting to future.
Hi Justin, I found this issue is caused by that 2 NatureID(EGLCore.NATURE_ID and EGLNature.EGL_NATURE_ID) are added into the .project file, but the value of them are same as each other in EDT source code. I'm not sure if it is necessary to remove one of them for EDT. And I'm wondering if you didn't delete it for some extensibility issue when porting RBD code to EDT. In RBD, they are different: EGLNature.EGL_NATURE_ID : com.ibm.etools.egl.core.EGLNature EGLCore.NATURE_ID : com.ibm.etools.egl.model.eglnature Would you please help me check it? Thanks very much!
There is no need to have two natures in EDT (one of these in RBD was a 'legacy' nature). I've removed "org.eclipse.edt.ide.core.EGLNature". I checked out every project from CVS and did a file search for anything referencing this ID and changed it to the other one (plugin.xml files must have this hard coded and cannot point to the Java constant). I kept both constants around, but now EGLCore.NATURE_ID just points to EGLNature.EGL_NATURE_ID. I also removed the old nature from .project files in CVS (e.g. the widgets). Existing projects in your workspace won't be affected by this change, when a nature doesn't exist it doesn't cause any errors (case in point: edt.compiler's .project file has had the old "com.ibm." nature IDs this entire time). I've verified that existing projects still work, new projects are created with just the one nature, and converting a project to an EGL project also adds just the one nature.
Created attachment 209319 [details] Patch removing the duplicate nature
Small correction: it was edt.mof.egl that had the "com.ibm" natures, not edt.compiler.
Verified in Version: 0.8.0.v201201152102-1CT-Fiv5_M5_LOR6Ka4.
