diff options
| author | Christian W. Damus | 2016-06-21 12:50:56 +0000 |
|---|---|---|
| committer | Gerrit Code Review @ Eclipse.org | 2016-06-22 11:50:21 +0000 |
| commit | a00dd8b4c6ca7badf2dc6ae10e1f9a7e28546e9f (patch) | |
| tree | 466601e6a8dd5e48df1ecd9d94c1f44b7e7573d1 /releng/dev/targetPlatform/portable/org.eclipse.papyrus.dev.portable.target.target | |
| parent | 2fc92a7ef3d6e9f1fa8ad93af5ab5442776eb339 (diff) | |
| download | org.eclipse.papyrus-a00dd8b4c6ca7badf2dc6ae10e1f9a7e28546e9f.tar.gz org.eclipse.papyrus-a00dd8b4c6ca7badf2dc6ae10e1f9a7e28546e9f.tar.xz org.eclipse.papyrus-a00dd8b4c6ca7badf2dc6ae10e1f9a7e28546e9f.zip | |
Bug 496439: [RSA Import] Give mapping traces to extension transformations https://bugs.eclipse.org/bugs/show_bug.cgi?id=496439
(cherry-picked from master)
Carry mapping traces forward from each transformation in the chain to the next. Provide a black-box library with custom operations that query the mapping traces to find sources for generated outputs because the standard invresolve and invresolveone operations only inspect the traces of the current transformation, not any previous.
Provide also a new API for execution of a transformation that automatically includes the traces, so that extensions can make use of them, too (otherwise, as currently in Papyrus-RT, they will always have to reimplement access to the executor pool, which is a detail that should be abstracted away from them).
Change-Id: Idd9f381bd525d0e40e94366d76afb0a4c679d1b9
Diffstat (limited to 'releng/dev/targetPlatform/portable/org.eclipse.papyrus.dev.portable.target.target')
0 files changed, 0 insertions, 0 deletions