[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [m2m-atl-dev] Plan to merge ATL_Dynamic_ResourceSet branch with HEAD
|
Hi Dennis,
I also plan to commit changes next week, but I think the scope differs
from yours: It consists on a "core" api, mainly dedicated to the EMFVM
and which will provide utilities for programmatic launch, ant launch
etc... I will give more details soon.
In the end we plan to leave the RegularVM for the EMFVM (for obvious
maintenance problematics), as soon as the RegularVM won't be used in ATL
other parts. For the moment it is not possible for us to do because some
components (debugger, compiler, parser) are strongly linked to the
RegularVM. So at this time, and after the API change will be effective,
the RegularVM and its drivers will be the same as before.
To summarize, the RegularVM & drivers are changeable, so you can commit
your changes on those parts. But we need to define the impact of your
ATL_Dynamic_ResourceSet branch on other components (launchconfigs ?
builder ? compiler ?).
As you may know, the EMF interactions defined in the EMFVM are quite
based on those defined under the EMF4ATL driver (but more simpler). So
the merge of your work will be useful to solve same issues in the EMFVM.
Best regards,
William Piers
Dennis Wagelaar a écrit :
Dear devs,
Some time ago, I've created the ATL_Dynamic_ResourceSet branch to deal
with the problem I've stated in my e-mail to this list of September
23rd, 2008. As I've done all the testing I could manage, I think it's
time to open up this code to all ATL developers. I've you've any
objections, please let me know as soon as possible. Otherwise, I plan
to go ahead with the merge next week.
Main changes:
* Models are no longer loaded via an AtlModelHandler. Instead, use an
AtlModelHandler to create a ModelLoader instance. It is recommended to
use only one ModelLoader instance per handler type. After you're done
with running ATL on the loaded models, you can just let go of the
ModelLoader instance and the garbage collector takes care of the rest.
* A call to Resource#unload() has been reintroduced in the UML model
handler to avoid memory leak. I've found no leak in the ATL code and
this leak also does not occur for any other meta-model than UML.
Kind regards,
Dennis Wagelaar
_______________________________________________
m2m-atl-dev mailing list
m2m-atl-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2m-atl-dev
begin:vcard
fn:William Piers
n:Piers;William
org:Obeo
adr:2 rue Robert Schumann;;lot 24;NANTES;;44408;France
email;internet:william.piers@xxxxxxx
title:MDA Consultant
tel;work:+33 (0)2 51 13 51 82
tel;cell:+33 (0)6 20 31 75 98
url:http://www.obeo.fr
version:2.1
end:vcard
