Didier Vojtisek
Didier Vojtisek
In case of 2 base classes that inherit from each other, it is normal to have 2 aspects that inherit from each other that each point to its base class....
Putting an annotation (@Aspect or other) on the wrong content crashes the annotation processor. (typically with a ClassCastException) The resulting file is completly broken with many message that aren't user...
The documentation is still unclear about how to call K3 aspects from pure Java see. https://dev.eclipse.org/mhonarc/lists/gemoc-dev/msg00007.html For example it should make clear what is the api part of the code...
for a correct IP, the copyright and licence field must be filled in all eclipse features
this includes java and xtend files (the eclipse releng tool helps to do the java files, but xtend files must be processed manually)
if we change the location for the k3 project (see  ) (this is useful when creating the project directly in a location managed by git for example) then use...
The @Contract + @Inv for design by contract with K3 cannot be used with the @Aspect annotations. this simple example (on top of ecore ) ``` xtend package hello_ecore import...
in the new K3 project wizard, the "reference existing ecore" browse button doesn't work in some situations. step to reproduce, open an editor, do some selection in it, then File...
The template generator that generates aspect from an ecore file currently supports single inheritance only (. (new K3 project, next, select _User Ecore Basic aspect_ template ) since we now...
The new K3 project wizard allows to create a plugin. Usually plugin offer an Activator. we should generate one in the wizard. If possible this activator shoud suggest the use...