[great-users] avoiding recompilation of UDM generated API-s

[Attila Vizhanyo]

Essentially we had these two solutions in mind.
I think we can also implement the smarter one (dirty bit solution) 
relatively easily.

--Attila


Sandeep Neema wrote:

>GReAT Guys,
>This issue was raised earlier regarding regeneration/recompilation of
>the UDM generated API-s for every smallest tweaks to transformation
>rules, even if it does not have any effect on the metamodels of
>transformation source/target.
>
>With some big paradigms this turns out unfortunately to be a big time
>sink, inviting a coffee trip every time one runs the transformation
>after making some mods, since the compilation of the UDM generated API
>with Release build settings takes a significant amount of time.
>
>One easy tweak I could see is to add a 'check box' in the master
>interpreter and let the user decide whether he wants UDM to be invoked.
>Alternately, a plug-in could be developed that effectively sets the
>'dirty bit' when any class diagram in the model is modified, since the
>last invocation of UDM.
>
>Please share any thoughts/suggestions, or workaround that you may have
>come up with -
>
>Thanks,
>Sandeep
>
>--
>Sandeep Neema
>Research Scientist,
>Institute of Software Integrated Systems, Vanderbilt University
>Phone: 615-343-9996
>Email: sandeep.k.neema at vanderbilt.edu
>
>_______________________________________________
>great-users mailing list
>great-users at list.isis.vanderbilt.edu
>http://list.isis.vanderbilt.edu/mailman/listinfo/great-users
>
>  
>