Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "MMT/QVTo/New and Noteworthy/Kepler"

< MMT
(Milestone 6)
Line 16: Line 16:
 
* [https://bugs.eclipse.org/394498 394498] The debugger can now switch between multiple transformations/libraries
 
* [https://bugs.eclipse.org/394498 394498] The debugger can now switch between multiple transformations/libraries
 
* [https://bugs.eclipse.org/397215 397215] null arguments may now be used with disjunctive mappings
 
* [https://bugs.eclipse.org/397215 397215] null arguments may now be used with disjunctive mappings
 +
* [https://bugs.eclipse.org/397218 397218] Argument/parameter type comparison is now properly done when dispatching a disjuncting mapping
 
* [https://bugs.eclipse.org/397959 397959] Overriding should no longer be confused by the presence/absence of a context
 
* [https://bugs.eclipse.org/397959 397959] Overriding should no longer be confused by the presence/absence of a context
  
Line 24: Line 25:
 
* [https://bugs.eclipse.org/358709 358709] resolveoneIn(...) no longer fails for override mappings
 
* [https://bugs.eclipse.org/358709 358709] resolveoneIn(...) no longer fails for override mappings
 
* [https://bugs.eclipse.org/376274 376274] Nested packages may now be used in metamodel mappings
 
* [https://bugs.eclipse.org/376274 376274] Nested packages may now be used in metamodel mappings
 +
* [https://bugs.eclipse.org/388329 388329] Deployed libraries are now excluded from the Select Transformation dialog
 +
* [https://bugs.eclipse.org/388331 388331] Contextless mappings on resolve operations are available on completion proposals
 
* [https://bugs.eclipse.org/388801 388801] Collection-type features are initialized to Set{} rather than Set{null}
 
* [https://bugs.eclipse.org/388801 388801] Collection-type features are initialized to Set{} rather than Set{null}
 
* [https://bugs.eclipse.org/397218 397218] Disjunct mapping dispatch no longer ignores the argument/parameter types
 
* [https://bugs.eclipse.org/397218 397218] Disjunct mapping dispatch no longer ignores the argument/parameter types

Revision as of 06:39, 19 March 2013

Eclipse QVT Operational New and Noteworthy items for the Kepler 3.3.0 release.

Milestone 2

  • 378940 Duplications of OCL 2.2 operations removed

Milestone 5

  • 302594 Inherited properties of accessed transformations are now available
  • 309762 Disjunction now considers overriding mappings
  • 310991 Inherited configuration properties of accessed transformations are now available
  • 377882 Resolve on a disjunction mapping no longer returns null
  • 388325 += is no longer ignored on a result variable
  • 392080 An initialized imported property is now part of the out extent
  • 392153 The execution of an accessed transformation is now included in the trace
  • 394498 The debugger can now switch between multiple transformations/libraries
  • 397215 null arguments may now be used with disjunctive mappings
  • 397218 Argument/parameter type comparison is now properly done when dispatching a disjuncting mapping
  • 397959 Overriding should no longer be confused by the presence/absence of a context

Milestone 6

  • 254962 Intermediate properties are no longer ignored when cloning
  • 296630 Local variables now contribute to completion proposals
  • 358709 resolveoneIn(...) no longer fails for override mappings
  • 376274 Nested packages may now be used in metamodel mappings
  • 388329 Deployed libraries are now excluded from the Select Transformation dialog
  • 388331 Contextless mappings on resolve operations are available on completion proposals
  • 388801 Collection-type features are initialized to Set{} rather than Set{null}
  • 397218 Disjunct mapping dispatch no longer ignores the argument/parameter types

Back to the top