Re: [viatra-dev] GEF5 integration merged into master

[Zoltán Ujhelyi <zoltan.ujhelyi@xxxxxxxxxxxxxxxx>]

Hi all,

one more thing to note with the new setup: I had to provide a toolchains.xml file for the Hudson-based builds in the repository [1]; this results in build failures for Gerrit changes not up-to-date with the current master. Simply rebasing the open changes should fix this issue automatically.

Sorry for the inconvenience,
Zoli

  [1] http://git.eclipse.org/c/viatra/org.eclipse.viatra.git/tree/releng/org.eclipse.viatra.parent/toolchains-hudson.xml
-- Zoltán Ujhelyi

Eclipse Technologies Expert
IncQueryLabs Ltd.

> On 2017. Apr 23., at 15:30, Zoltán Ujhelyi <zoltan.ujhelyi@xxxxxxxxxxxxxxxx> wrote:
> 
> Hi all,
> 
> as mentioned in this week’s meeting I have successfully merged a set of changes to master that use the new GEF 5 Zest version for graph visualization instead of the previously used, unreleased GEF4 versions [1].
> 
> This change updated the following features of VIATRA:
> 
> * Rete visualizer
> * Local search debugger
> * Zest integration for the Viewers addons
> 
> GEF5 depends on Java 8 and JavaFX; JavaFX requires some additional setup to work correctly that is mostly done by the e(fx)clipse component. This means, the VIATRA target platform now includes e(fx)clipse and GEF5, and some (but not all) plug-ins rely on Java 8.
> 
> =====
> The following steps are required to update the development environment:
> =====
> 
> 1. After current changes are checked out, execute Oomph. It will install a few JavaFX-related components into the host; and add GEF 5 and e(fx)clipse to the target platform. No manual steps are necessary.
> 2. Each run configuration that executes the VIATRA user interface and wants to use the Zest-dependent components has to specify an additional JVM argument: -Dosgi.framework.extensions=org.eclipse.fx.osgi
> 3. VIATRA builds configurations are to be updated via additional classpath entries, see [2]. The Guice fragments might be optional, but I did not try to execute the build without those values.
> 
> 
> 
> Known issues:
> * RCPTT tests cannot use JavaFX based views. For this reason, a few tests from our test suite were turned off, as they cannot run.
> * JavaFX on SWT does not work on GTK3 [3]; if you try to open a view with JavaFX on GTK3, the JVM crashes… As a workaround, the environment variable SWT_GTK3 has to be set to the value 0. This was the cause of the RCPTT test failures on Jenkins.
> * OpenJDK (as used on Linux) does not always include JavaFX support by default. E.g. on Ubuntu either the OpenJFX package has to be installed, or Oracle JDK is necessary to run the graphical features.
> 
> If anyone has any question, or something went wrong during this merge, feel free to report any issues either in this thread or privately.
> 
> Best regards,
> Zoli
> 
> [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=472850
> [2] http://git.eclipse.org/c/viatra/org.eclipse.viatra.git/tree/releng/org.eclipse.viatra.parent/pom.xml?#n154
> [3] https://bugs.openjdk.java.net/browse/JDK-8087516
> -- Zoltán Ujhelyi
> 
> Eclipse Technologies Expert
> IncQueryLabs Ltd.
> 
> _______________________________________________
> viatra-dev mailing list
> viatra-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/viatra-dev