[news.eclipse.technology.gmt] Re: [MOFScript] Does "unprotect" already w

["Gøran K. Olsen" <Goran.K.Olsen@xxxxxxxxx>]

Hi Daniel,

The unprotect functionality you are reffering to, are unfortunately not 
implemented in the current version 1.1.10.
It is however in progress, but at the time of writing I can not give any 
fixed date for when it will be finished.

The only way of protecting your files are by placeing the file statement 
inside a fileExists() block, in this way existing files will be kept 
untouched. If you want to regenerate a file it must be removed from your gen 
directory.

/Gøran



"Daniel Pieper" <nospam@please.!> wrote in message 
news:eguh0j$6jv$1@xxxxxxxxxxxxxxxxxxxx
> Hi,
>
> playing around with MOFScript 1.1.10 for a
> while now and am quite impressed.
>   The only thing I tried that WONT work so far
> is creating "unprotected" regions to protect user
> changes in successive transformations.
>
> What I have done so far:
>
> - Check "Traceability active" in Preferences
> - Having a rule sth. like
>    [...]
> unprotect {
>     <% change it! %>
>   }
>    [...]
>
> Can't get it to work! Please tell me it's my fault
> because I'd really like to use this wonderful tool
> in production environments which would be almost
> impossible to do if user input was lost after every
> transformation.
>
> Thanks in advance,
>   Daniel