Skip to main content
Jump to: navigation, search

Difference between revisions of "VIATRA/Releases/NewAndNoteworthy1.5"

(Query Maven plugin)
Line 24: Line 24:
 
* [https://www.youtube.com/watch?v=TaLvKgfxQNg# VIATRA transformation debugger 0.15.0 feature demonstration screencast]
 
* [https://www.youtube.com/watch?v=TaLvKgfxQNg# VIATRA transformation debugger 0.15.0 feature demonstration screencast]
  
== Query Maven plugin ==
+
== Using project dependencies in Query Maven plugin ==
  
 
You can now use ''useProjectDependencies'' in your configuration instead of adding metamodels as Maven dependencies. This is especially useful when the metamodels are not available as Maven artifacts.
 
You can now use ''useProjectDependencies'' in your configuration instead of adding metamodels as Maven dependencies. This is especially useful when the metamodels are not available as Maven artifacts.

Revision as of 09:06, 1 December 2016

Support for more number literals in query language

All number literals supported by Xtend (see documentation for details) are now directly supported by the VIATRA Query language.

pattern circleConstantDiameter1(c : Circle) {
  Circle.diameter(c, 3l);
  Circle.area(c, 9.42f);
}

Performance improvements in the incremental query evaluator (Rete engine)

Constant values (more precisely constant-value filtering) within patterns are now handled more efficiently in many cases. In a proprietary code base, specifically for entire query packages where this feature is heavily used, we have observed a reduction between 15-30% in the memory footprint of Rete.


Remote debugging support added to the VIATRA model transformation debugger

The VIATRA model transformation debugger (introduced in VIATRA 1.3.0) has undergone a series of architectural and backend-related changes. The current, 0.15.0 version of the debugger now enables the user to connect to remote VIATRA model transformations, while maintaining the user experience introduced in the previous version. This way, model transformations running on remote JVM instances can be analysed much more straightforward way.

Sounds interesting? Make sure to check out the following resources:

Using project dependencies in Query Maven plugin

You can now use useProjectDependencies in your configuration instead of adding metamodels as Maven dependencies. This is especially useful when the metamodels are not available as Maven artifacts.

<configuration>
  <useProjectDependencies>true</useProjectDependencies>
<configuration>


For more details, see the following wiki page.

Back to the top