|Re: How to import Viatra via Maven [message #1826309 is a reply to message #1826308]
||Thu, 23 April 2020 10:03
| Zoltan Ujhelyi
Registered: July 2015
this behaviour is by design, the viatra-transformation-runtime is only a wrapper for a few Eclipse plugins that will be loaded transitively when you declare a dependency on the given element. The Petri net simulator example  shows you how to create a project that includes VQL files to be translated to query generated code by the build and also includes dependencies to the transformation runtime. The example was created a few versions ago, but it should show what can you expect from our Maven integration.
The reasons for this approach are two-fold: (1) VIATRA is developed as a large number of plugins, but normally you would not require to manage them separately, so these references bundle them together in reusable form, and (2) the plugins of VIATRA are translated with Tycho and use dependencies from p2 repositories instead of Maven Central; the Maven wrapper plugins replace these dependencies with plain Maven ones, making it simpler to reuse outside Eclipse environments. This is not entirely the behaviour one expected from a Maven-based project, but VIATRA was developed as an Eclipse plugin first so there were some issues we had to work around when going for plain Java applications.
Powered by FUDForum
. Page generated in 0.01666 seconds