Skip to main content
Jump to: navigation, search

Difference between revisions of "MMT/QVTo/New and Noteworthy/2019-09"

< MMT
(3.10.4 (June 2021))
(3.10.5 (December 2021))
Line 59: Line 59:
 
This release provides further improvements to the support for blackbox development in the workspace:
 
This release provides further improvements to the support for blackbox development in the workspace:
  
  [https://bugs.eclipse.org/573449 573449] Blckboxes may now use workspace resources.
+
  [https://bugs.eclipse.org/573449 573449] Blackboxes may now use workspace resources.
 
  [https://bugs.eclipse.org/574706 574706] Blackbox class loading and analysis improved.
 
  [https://bugs.eclipse.org/574706 574706] Blackbox class loading and analysis improved.
  
Line 66: Line 66:
 
  [https://bugs.eclipse.org/573718 573718] 'out' parameters are no longer cloned as part of the trace.
 
  [https://bugs.eclipse.org/573718 573718] 'out' parameters are no longer cloned as part of the trace.
 
  [https://bugs.eclipse.org/577310 577310] Cyclic build paths no longer crash the QVTo buillder.
 
  [https://bugs.eclipse.org/577310 577310] Cyclic build paths no longer crash the QVTo buillder.
 +
 +
=3.10.6 (March 2022)=
 +
 +
This release provides further improvements to the support for blackbox development in the workspace
 +
and a significant simplification in the import of metamodels.
 +
 +
Whereas it used to be necessary to use a modeltype sttement to import a model name such and then
 +
map the model name to the actual model in the .settings/org.eclipse.m2m.qvt.oml.mmodel.urimap,
 +
it is now possible for the modeltype to reference the actualmodel directly; the
 +
.settings/org.eclipse.m2m.qvt.oml.mmodel.urimap file is now obsolete.
 +
 +
== M1
 +
[https://bugs.eclipse.org/573449 573449] JDT Blackboxes now reload correctly.
 +
 +
== RC1
 +
[https://bugs.eclipse.org/571406 571406] Blackbox analysis avoids searcging irrelevant paths
 +
[https://bugs.eclipse.org/577618 577618] Metamodels may be imported using paltform: URIs
 +
[https://bugs.eclipse.org/577992 577992] Blackboxes no longer fail with dynamic metamodels.
 +
[https://bugs.eclipse.org/578625 578625] Blackboxes may be used after serializing to a *.qvtox file.
 +
[https://bugs.eclipse.org/578955 578955] Blackboxes may be imported wth access or extends.

Revision as of 16:50, 9 March 2022

3.10.0 (September 2019)

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

3.10.1 (December 2019)

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.

3.10.2 (June 2020)

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

3.10.3 (March 2021)

472482 QVTo now integrates with JDT to resolve blackbox modules on the classpath of a Java project. This makes it possible to get rid of the 'No blackbox implementation found' warning.

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 @Module(packageURIs={"http://www.eclipse.org/emf/2002/Ecore"}).

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.

3.10.4 (June 2021)

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 located in required bundles.

Further improvements:

573659 QVTo projects are now able to import *.qvto units from required plug-in projects (requires PDE).

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 searched in the corresponding package registry.

566236 Loading *.qvto units in standalone mode is now possible even if the path to a unit contains whitespace.

472466 The return type of multiple Sequence operations such as excluding was corrected to Sequence (fixed by OCL).

3.10.5 (December 2021)

This release provides further improvements to the support for blackbox development in the workspace:

573449 Blackboxes may now use workspace resources.
574706 Blackbox class loading and analysis improved.

Further improvements:

573718 'out' parameters are no longer cloned as part of the trace.
577310 Cyclic build paths no longer crash the QVTo buillder.

3.10.6 (March 2022)

This release provides further improvements to the support for blackbox development in the workspace and a significant simplification in the import of metamodels.

Whereas it used to be necessary to use a modeltype sttement to import a model name such and then map the model name to the actual model in the .settings/org.eclipse.m2m.qvt.oml.mmodel.urimap, it is now possible for the modeltype to reference the actualmodel directly; the .settings/org.eclipse.m2m.qvt.oml.mmodel.urimap file is now obsolete.

== M1

573449 JDT Blackboxes now reload correctly.

== RC1

571406 Blackbox analysis avoids searcging irrelevant paths
577618 Metamodels may be imported using paltform: URIs
577992 Blackboxes no longer fail with dynamic metamodels.
578625 Blackboxes may be used after serializing to a *.qvtox file.
578955 Blackboxes may be imported wth access or extends.

Back to the top