Community
Participate
Working Groups
Xtext 2.2 reports "Packages should be imported by their namespace URI." warnings for platform/resource imports. This is wrong. When a meta-model is under development, the http: form should refer to the Java package the platform:/resource or platform:/plugin to the Ecore model in each case falling back from open project to installed plugin. Only the Ecore model should be subject to live update, therefore the platform:/resource forms should be preferred. [And prior to Xtext 2.2 http: forms just didn't work.]
And, if an http: is resolved to a development resource you either require that class path references the project target genmodel is correct or have to scan every file to try to locate the file that may be lurking under some proprietary text to ecore encoding such as oclinecore or xcore. The first goes hopelessly wrong when cutting and pasting debug test examples, the second burns up my computer cycles with pointless indexing.
