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 "VIATRA/Releases/Query/NewAndNoteWorthy0.7.2"

Line 8: Line 8:
 
* {{bugstrike|420935}} Pattern validator trips on convoluted pattern with  many == constraints
 
* {{bugstrike|420935}} Pattern validator trips on convoluted pattern with  many == constraints
 
* {{bugstrike|417303}} Query specification registry should give information on which extension point failed to load
 
* {{bugstrike|417303}} Query specification registry should give information on which extension point failed to load
 +
* {{bugstrike|422775}} Support "run once" query evaluation over non well-behaving derived features
 +
* {{bugstrike|420303}} Make the invocation of XBaseEvaluator.init() conditional
 +
* {{bug|423298}} Query is not entirely updated when resource is reloaded
 +
 +
  
 
== Viewers issues ==
 
== Viewers issues ==

Revision as of 02:19, 16 January 2014

Known issues affecting version 0.7.1

Issues with corresponding Bugzilla entry

  • bug 419439 [Viewers] edges disappear if the source or target item is changed
  • bug 419985 GMF dependency in viewers.runtime.zest
  • bug 420934 Engine fails during variable unification for convoluted pattern
  • bug 420935 Pattern validator trips on convoluted pattern with many == constraints
  • bug 417303 Query specification registry should give information on which extension point failed to load
  • bug 422775 Support "run once" query evaluation over non well-behaving derived features
  • bug 420303 Make the invocation of XBaseEvaluator.init() conditional
  • bug 423298 Query is not entirely updated when resource is reloaded


Viewers issues

  • label updates, arrow styles, viewer initialization, disposal

Compatibility issues

  • Due to changes in GEF4 Zest API, versions 0.1.0.201310190205 or later are required

Other issues

  • Logger output for query-based features when query violates multiplicity contracts

Back to the top