Community
Participate
Working Groups
Dynamic packages that are contributed not as generated code but as emf.dynamic_package extension point can not be used as basis for dynamic Exeed model editing. The simple fix solves this issue (attached to the bug). The trick is that EPackage.Registry.INSTANCE contains instances of EPackage.Descriptor and not EPackage (due to lazy loading and resource saving concerns), however once you would need to have EPackage you can simply call EPackage.Descritptor#getEPackage(). Patch is doing only that.
Many thanks for reporting this and for suggesting a solution. Something must have gone wrong while uploading the patch - but this appears to be straightforward to fix anyway.
Created attachment 178705 [details] patch here is a path again. Trick is to display package list directly without resolution of Epackage.Descriptors into Epackage instances. BTW the Registered package view has also this isssue (do not support EPackage.Descriptor)
Thanks. For some reason I can't apply the patch directly but I think I got the gist of it and will fix this in a few more places. The fix will appear in the next interim version we'll be rolling out in the next few days.
Fixed in the SVN. Fix will appear in version 0.9. Thanks!
Fixed in the latest interim version (0.8.9.201011041158).
Fixed in 0.9.0.