subversion/sourcecontrol and regenerating

Posts   
 
    
mdissel
User
Posts: 92
Joined: 16-Sep-2003
# Posted on: 20-Jan-2005 14:36:48   

Hello

When using sourcecontrol tools, regenerating the code results in a complete commit of the files, instead of only the changed files.

Maybe you can add an option to not include the "Code is generated on: <DateTime.Now>" in the generated code... Or even better. Only generate the sourcecode for the objects that have been changed after the last code generation (and/or make this optional when generating the code (only changed objects or complete)

Thanks

Marco

Otis avatar
Otis
LLBLGen Pro Team
Posts: 39588
Joined: 17-Aug-2003
# Posted on: 20-Jan-2005 17:06:45   

It's planned to have an option not to emit the time etc. in a file, but I'm not quite sure how to solve it, without having to compare complete files. The option to only generate code for changed items is not something which is possible, as it would create dependencies.

Frans Bouma | Lead developer LLBLGen Pro
mdissel
User
Posts: 92
Joined: 16-Sep-2003
# Posted on: 20-Jan-2005 20:22:52   

maybe first create a tmp file and do the processing and afterwards do a diff on the files.

Of course optionally because this will take longer then just replacing the files, but i think this usefull for all the sourcecontrol users.

Thanks

Marco

Otis avatar
Otis
LLBLGen Pro Team
Posts: 39588
Joined: 17-Aug-2003
# Posted on: 21-Jan-2005 10:15:37   

Well, in the current upgrade-in-progress the plan is to modify the code-generator in such a way that regions marked by the user are preserved, so it has to generate to a textbuffer in-memory anyway, so checking what's changed isn't that bad. However what can't be avoided is that if the time is written into a file, it still looks as if it's changed. So the only option there is to remove teh time from the template header.

This can only be done if there is some sort of log being created which files were changed during the generation process, as it is otherwise impossible to track down when a file was generated (and I really would like to keep that option). I don't like a separate log though, as it can get lost/overwritten and the information is gone.

I'll think of something. simple_smile

Frans Bouma | Lead developer LLBLGen Pro