|Re: [Acceleo]How to protect user code by signature changes [message #512449 is a reply to message #512228]
||Fri, 05 February 2010 08:23
| Laurent Goubet
Registered: July 2009
This is a multi-part message in MIME format.|
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Protected code will never be removed through generation, except if :
1) You change the marker of the protected area
2) You've put "@generated" on your class and haven't changed this tag
in-between generations, causing JMerge to remove the old operation
Acceleo generations aren't tied to their target : it doesn't know your
generating code. Method names thus cannot alter the generation process.
However, Eclipse's jdt can alter your code ; for example if you've set
it to automatically remove unused methods.
> Hi All,
> We have been generation classes using the protected functionally for writing
> user code in the operation body which works fine.
> If we change the operation name or signature of the operation the old
> operation including the user code is removed.
> How do we specify the old operation not to be removed?
Content-Type: text/x-vcard; charset=utf-8;
Powered by FUDForum
. Page generated in 0.02642 seconds