[566196] Ensures a common log configuration for VIATRA runtime

Since a long time VIATRA had the ViatraQueryLoggingUtil class that was
responsible for a common logging configuration, but it was not used
consistently in the various components of VIATRA. This change
centralizes its usage, and in order to make sure the output is more
readable, duplicate name entries are removed.

Change-Id: I8eaabcfb7acae414450ea8707e930731a90bee37
Signed-off-by: Zoltan Ujhelyi <zoltan.ujhelyi@incquerylabs.com>
8 files changed
tree: 2351f8c3baae85410a03434cbe15de696a1165b2
  1. addon/
  2. artwork/
  3. documentation/
  4. dse/
  5. integration/
  6. maven/
  7. query/
  8. releng/
  9. transformation/
  10. .gitattributes
  11. .gitignore
  12. .mailmap
  14. LICENSE.md
  15. NOTICE.md
  16. README.md


The Eclipse VIATRA framework is a model and data transformation tool that helps move information back and forth in the most efficient way. The platform focuses specifically on event-driven and reactive transformations, which happen on-the-fly as the models change.

VIATRA is a long-running project that incorporates the results of over 15 years of active research and development. VIATRA offers

  • a domain-specific language for graph queries and reactive transformations
  • a Java runtime library which is scalable and easy to embed.

VIATRA primarily targets model-driven engineering tools based on the industry-standard Eclipse Modeling Framework, though it can be used in other contexts as well. VIATRA is an enabling technology and its biggest benefit is the power it gives you to close abstraction gaps. These exist in every data-driven application where structured data needs to be moved across various languages or representation formats.

VIATRA helps you create model transformations that convert objects between languages. Trivial transformations (i.e. copying pieces of data from one document to another) are easy with any general purpose programming language such as Java. In contrast, VIATRA gives you easy-to-use and reusable programming patterns to address non-trivial transformations, such as

  • Changing of structure, i.e. converting a UML model to a source code.
  • Derived data and abstractions: manipulating data during conversion, e.g. filtering information for creating ‘abstract views’
  • Combining multiple sources of information in a significant way to produce a new result, e.g. when creating data streams for dashboards
  • Changing structure: projection of data containing only relevant information during the conversion phrase

Most important links


All code in this repository is available under the Eclipse Public License v2.0: http://www.eclipse.org/legal/epl-v20.html