Community
Participate
Working Groups
The new models supporting XML2XML and Model2Text are useful to ATL and QVTo as well as QVTd. How can they be made generally available? Clearly neither ATL nor QVTo wants a dependency on QVTd so they cannot be in QVTd. Perhaps they could be in OCL, but ATL has its own OCL. Perhaps they could be in EMF, but that would be unwelcome bloat. Perhaps we have a new neutral EMFT project - ugh! If instead QVTd has a self-standing 'useful' models feature, other projects can redistribute the feature or its plugins as part of their own distributions; just like OCL redistributes LPG from Orbit. Multiple redistributions of the identical qualified QVTd versions should be no problem. Candidate content: - org.eclipse.qvt.text - the Model2Text Ecore model - org.eclipse.qvt.xml - the XML Ecore model - org.eclipse.qvt - the raw OMG specification models for QVT 1.3 Awkward detail. The manually added toString() support uses an OCL utility routine to escape awkward characters. Is this cloned and hidden within the model plugin? Is an org.eclipse.qvt.common needed to future-proof additions? ?? Is this the start of a slippery slope that evolves to full ATL Zoo distribution ?? Do we need an org.eclipse.zoo project ?
