Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
MMT/QVTo/New and Noteworthy/2019-09
Eclipse QVT Operational New and Noteworthy items for the 2019-09 (3.10.0) release.
3.10.0 Milestone 3
550053 The root QVTo metamodel EPackage is now statically rather than lazily registered
Eclipse QVT Operational New and Noteworthy items for the 2019-12 (3.10.1) release.
Nothing has changed, but changes to the Eclipse Foundation infrastructure merit a maintenance release.
Eclipse QVT Operational New and Noteworthy items for the 2020-06 (3.10.2) release.
3.10.2 Milestone 1
561707 Regression for implicitly contained elements fixed
3.10.2 Milestone 2
562732 Java 8 now explicitly rather than implicitly required for UI functionality
562175 When creating a new QVTo plug-in project, the directory for *.qvto files is now automatically registered by adding an extension to the plugin.xml file. Imports of *.qvto files can thus be resolved against this directory in an Eclipse environment.
565747 QVTo now aims to automatically infer the namespace URIs needed to resolve blackbox operations. For example, to resolve a blackbox operation that uses types from the Ecore metamodel, the corresponding Java class no longer needs to be annotated with
566216 The Java blackbox resolution now conforms to the Liskov substitution principle. This makes it possible for a Java blackbox method to return a subtype of the QVTo return type or to accept supertypes of the QVTo parameter types.
566230 The Java blackbox resolution now takes into account the argument types of parameterized types. When a Java blackbox method uses a parameterized type, its argument types must be compatible with those of the corresponding QVTo type, which prevents invalid bindings between QVTo types and Java types.
This release improves the support for blackbox development in the workspace:
573449 It is now possible to resolve blackboxes against dynamic metamodels from the workspace. This is achieved by analyzing the corresponding GenModel.
573752 Resolving blackboxes is now possible even if the underlying metamodels are from required bundles.
570407 QVTo can now handle metamodels that use a relative URI (such as
../../org.eclipse.emf.ecore/model/Ecore.ecore) to reference other metamodels. If they are not present in the workspace, the referenced metamodels are located in the corresponding package registry.
566236 Loading *.qvto units in standalone mode is now possible even if the path to a unit contains whitespace.