You may want to have a look at EMF loophole https://github.com/mbarbero/emf-loophole. It lets you define a model on top of genmodel. It adds some nice features like generation of custom classes and what you want: deleting the generated files each time you re-generate.
You could make it clearer that the URLs are update sites.
Unfortunately I think the limitation that it doesn't work for
cross-referencing genmodels is a killer for me.
It would help to see an example and know what will happen before
installing something that may interfere with genmodel.
Regards
Ed Willink
On 03/10/2013 02:37, Mikael Barbero wrote:
> Hi,
>
> Have a look at EMF loophole https://github.com/mbarbero/emf-loophole.
> It lets you define a model on top of genmodel. It adds some nice
> features like generation of custom classes and what you want: deleting
> the generated files each time you re-generate.
>
> Hope this helps.
Does your code contain any hand written changes? If not, you could just
delete the Java packages involved. If so, what are you expecting to
happen to that? If you define the model in Xcore (you can export your
existing *.genmodel to *.xcore) and generate to the default src-gen
folder, a clean build will delete all the generated code...
On 02/10/2013 8:03 PM, Michael Vorburger wrote:
> Is there a way to have Generate (Model) Code deleting all prev. gen.
> code?
>
> Some flag on the *.genmodel... or would this be possible with a custom
> Facade Helper Class?
>
> I do understand that all the magic @generated merge "feature" would be
> lost - never mind.
>
> Or is this an Enhancement? Bugzilla welcome, or waste of time?
>
> Just a thought.