eclipse-qvtd / org.eclipse.qvtd

Eclipse Public License 2.0
0 stars 0 forks source link

[cg] Non-standard JET templates #317

Open eclipse-qvtd-bot opened 14 hours ago

eclipse-qvtd-bot commented 14 hours ago

| --- | --- | | Bugzilla Link | 522560 | | Status | NEW | | Importance | P3 normal | | Reported | Sep 21, 2017 04:25 EDT | | Modified | Sep 21, 2017 05:37 EDT | | Depends on | 485089, 485764 | | Reporter | Ed Willink |

Description

This bug traces the progress in removing non-standard JET templates.

Currently /org.eclipse.qvtd.compiler/templates/model/*.jet has fixes for Bug 485089 and Bug 485764.

EMF 2.14M2 has a fix for Bug 485764, so that could be removed iff we raise the EMF lowerbound to 2.14. But we still need Bug 485089 so we might as well retain Oxygen compatibility during Photon development.

eclipse-qvtd-bot commented 14 hours ago

By Ed Willink on Sep 21, 2017 05:37

In order to incorporate the other EMF 2.14M2 whitespace changes the GIT history shows commits for:


EMF 2.14 via Bug 428088 introduces new API to support @deprecated tags. This GenModel API is not available in Oxygen/EMF 2.13 and since it is at JET time it does not need to be guarded by the prevailing run-time level. We must therefore decide:

a) suppress the 2.14 @deprecated support for now\ b) falsely claim to run on 2.13 - users get CG failures\ c) redirect the new @deprecated support to stubs on EMF 2.13\ d) continue unchanged

There are about 80 redirections to about 5 new API methods. Possible but tedious and a significant amount to review/fixup for the next change.

Suggest: stay as is until M6, then impose an EMF 2.14 lowerbound.

(Impact the temporarily missing @deprecated support is for autogenerated QVTd models; will anyone care. Indeed what does the new support actually do?)

Branch ewillink/522560 shows the history awaiting exploitation at M6.