William Piers a écrit :
At this time the emfvm is launched using dependently of
org.eclipse.m2m.atl.debug (see class
/org.eclipse.m2m.atl.engine.emfvm/src/org/eclipse/m2m/atl/engine/emfvm/AtlEMFSpecificVM.java).
This solution will probably change in the future, so you better have
to inspirate from this code :
/org.eclipse.m2m.atl.examples/src/org/eclipse/m2m/atl/examples/EMFVMLauncher.java
Those launching facilities will be soon refactored in order to
provide them directly in the VMs. The last class I reference is a
kind of temporary "workaround" so I advise you to copy it into your
solution instead of make a dependency on
org.eclipse.m2m.atl.examples. At least this class (or a better
interface) will be integrated in an other plugin.
If I understand, the EMFVMLauncher.java class helps to launch the VM.
But what I need is to declare a new one. I saw that the code is
launched from the ASM.java class (EMFVM). But it seems to need
modifications in the ExecEnv to add debugger information ... It's not
possible for me if I want to be "ad-hoc" with ATL.
Shouldn't it be better to wait for the refactoring of these launching
facilities ?
Thank you for your answers.
Best Regards,
Arnaud GIULIANI.
_______________________________________________
m2m-atl-dev mailing list
m2m-atl-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2m-atl-dev