we're presently using GMF 2.0 M3 and we have some severe issues with
incremental code generation.
A very simple case is for instance to add an attribute in the ecore
model, change a related mapping in gmfmap and then regenerate everything
(according to "normal procedure" - regenerate the generator model,
generate diagram code etc.).
It is obvious though that source files which should be regenerated due
to these changes are "sometimes" not, i.e. some IParserProvide
implementations, some of which have @generated NOT methods.
The only workaround so far is to safe any manually modified files,
delete everything, regenerate and merge the manual changes back in, but
that's quite cumbersome.
Is this a known issue and/or is there some way to force the code
generator to regenerate everything to avoid that some previously
generated files are not touched even if the should get regenerated ?