[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[incquery-dev] xcore & eiq status
|
Hi
A quick overview about the status of the xcore stuff:
(1) The @Ecore annotation doesn't seem to have any effect. If you
specify a custom URI, it will not be written to the plugin.xml.
It is also interesting, that the runtime Xtext index contains the
EPackage with the new custom URI. The original import in the
eiq files with the package URI "library" will not be valid anymore, you
can (and should) use the new one, even if the plugin.xml contains the
wrong entry.
This needs to be investigated with the help of Ed.
(2) I am not sure about the plugin.xml rewriting problems, I cant
reproduce it deterministically. I tried to erase all the contents of the
plugin.xml and invoke the builder again, and the contents have been
written properly. Nevertheless, a full clean usually will result in the
absence of the gen_package extension point definition and the query
specification extension points. The derived feature extension points are
always generated.
(3) Performance can be really poor in the xcore & EIQ scenario. Simply
adding a new pattern will result in a long building time.
(4) When we reach the point that everything is generated properly into
the plugin.xml, then the generated use case works just fine!
I will address (1), but I am going to need help with (2).
Cheers,
Tomi
