Community
Participate
Working Groups
In Bug 323878, a variety of problems with synonym meta-models are discussed. In https://bugs.eclipse.org/bugs/show_bug.cgi?id=323878#c7 it is suggested that "Perhaps EMF should have a workspace preference option so that all model loading favours development-time over run-time resources. Developers could set it and get better behaviour. Normal use would be unaffected." EMF currently has no workspace preference page, so this is new. The philosophical goal of 'the' option is to favour development-time meta-models over run-time models wherever possible. Ideally, all aspects of every plug-in project loaded in the development workspace should fully occlude any same-named plug-in in the run-time workspace. Therefore, xsi:schemaLocation should be favoured over a plugin registration. platform:/resource should be favoured over platform:/plugin. ?? alternate extension-point readers use development-time projects ?? ?? development workspace project models appear in the 'static' package registry ?? -- This last option would resolve the difficulty that meta-modeling tools have in resolving meta-models in their own workspace.
It's not clear how this is different from the issues discussed in https://bugs.eclipse.org/bugs/show_bug.cgi?id=220218. We really don't need two bugzillas to cover that issue. If this issue is about xsi:schemaLocation should be favoured over a plugin registration that's a small thing handled in the XMI plugin and available the client's discretion. The rest sounds grandiose and I don't fell like explaining again that the running IDE itself must behave a certain way. It must resolve platform:/plugin to the installed resources. That's what the installed plugins are expecting. How things behave in editors or in other parts of the system is another story. That's why 220218 talks about providing a different registry not some global option/preference that affects the entire JVM. So either refocus this on a resource loading option or I'll return it as a duplicate.
Yes. I guess it is a duplicate. An xsi:schemaLocation option would be nice, but would just move the boundary of where development resources do/don't work. Without full plugin occlusion it is not a safe development environment, just a hazardous but often useful hybrid. *** This bug has been marked as a duplicate of bug 220218 ***
