[Acceleo] keeping track of model changes on generation [message #911804] |
Wed, 12 September 2012 10:57 |
Farzad Sedghi Messages: 2 Registered: September 2012 |
Junior Member |
|
|
Hi,
I'm new to Acceleo and it's very interesting for me. There is one thing about generation in Acceleo for which I could not find any clear answer yet. I really like to know if Acceleo keeps track of changes in the input models between the current and its previous run, to regenerate only the affected parts of code. As far as I know it is very important in large projects for at least two reasons:
1. performance: there is no need to process all the models and run all the templates and write them back to disk, in order to have the effect of a small change in one of the models.
2. version control: Although it may not be a good practice to do version control for generated files, there are still cases where this is needed. Generation of all the files when the content of most of them are the same as before can confuse version control tools like CVS. So the developer should spend time or do some tricks to extract the real changed files among all the generated files.
Is there a solution for this problem in Acceleo? As mentioned above, keeping the track of model changes can be a solution, which is available in tools like Xpand for EMF models. Is this solution or any other available in Acceleo?
cheers.
[Updated on: Sun, 16 September 2012 23:48] Report message to a moderator
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03124 seconds