|Re: [Acceleo 3] Update in Model reflects regeneration [message #653118 is a reply to message #653102]
||Tue, 08 February 2011 14:57
| Laurent Goubet
Registered: July 2009
This is a multi-part message in MIME format.|
Content-Type: text/plain; charset=UTF-8; format=flowed
This is expected. Acceleo knows where it generates code... It doesn't
know anything else. In the case you are describing, Acceleo would need
to know that "before, there was a Class named 'ClassA', where is it
now?"... not to mention the case where you are deleting a class that
didn't generate anything (let's say you had a filter and didn't generate
anything for the class named "ClassA" for example).
Acceleo cannot infer such information by itself, as it does not keep
track of the "previous" generations.
This is in the scope of another of our projects, Obeo Traceability
(http://obeo.fr/pages/obeo-traceability), which would be able to tell
you that "ClassA.java hasn't been generated"... With Acceleo alone,
you'll have to manually delete the "not generated" file.
On 08/02/2011 15:07, Peter wrote:
> I am having a situation that at one time I added a UMLClass, for e.g
> ClassA, in the Model and run the generation, it will generate ClassA.java
> Now if I remove ClassA in the Model and rerun the generation to the same
> output location, I expected that ClassA.java should be deleted, but it
> didn't. Will Acceleo handle this case automatically or I have to
> manually compare and delete the file myself?
> Thanks for any response,
Content-Type: text/x-vcard; charset=utf-8;
Powered by FUDForum
. Page generated in 0.01720 seconds