Bugzilla – Full Text Bug Listing
| Summary: | [Generator] Generation corrupts Eclipse file system. | ||
|---|---|---|---|
| Product: | [Modeling] EEF | Reporter: | Miles Parker <milesparker> |
| Component: | General | Assignee: | EEF Inbox <emft.eef-inbox> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | major | ||
| Priority: | P3 | CC: | sbouchet, stephane.begaudeau |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Mac OS X - Carbon (unsup.) | ||
| Whiteboard: | |||
See but 364100 for cause of generation issue. Yes, Eclipse does not seems happy with these funny classes names. BTW, EEF should not generates such a classname. the template used to calculates the Class name throw an error and this is causing the problem. I'll take a look at the linked bug. The Eclipse EEF team has worked over the past few months on a brand new runtime using a reflective approach which can be used more easily with Eclipse Sirius. Since we do not plan to continue to work on the old runtime and its code generation approach, I will close this issue for now. If you want to contribute, you can reopen this issue and submit a contribution to the project thanks to our Gerrit: https://git.eclipse.org/r/#/admin/projects/eef/org.eclipse.eef |
I had a code generation issue, and when the code was generated it tried to use a class with the Java identifier as Org.eclipse.emf.ecore.impl.DynamicEObjectImpl@2d4aa09f. Obviously that didn't work. :) public static class Org.eclipse.emf.ecore.impl.DynamicEObjectImpl@2d4aa09f(eClass:Org.eclipse.emf.ecore.impl.EClassImpl@7e773df3(name:OclInvalid_Class)(instanceClassName:Null)(abstract:False,Interface:False)) { } In fact it worked so badly that Eclipse choked on the resulting directory structure on refresh. (I was able to fix it by deleting the offending directories from my OS.)