Rodin Platform 1.2 Release Notes

From Event-B
Revision as of 17:38, 15 January 2010 by imported>Nicolas (→‎Known Issues)
Jump to navigationJump to search

What's New in Rodin 1.2?

TODO: List here the new features and improvements.

  • Migration to Eclipse 3.5 (Galileo)


TODO: Inform here of some specific system requirements (version of Java, etc).

External plug-ins

TODO: Describe here the available plug-ins, and the supported versions for this release.


TODO: Add here a link to download the platform.

Fixed Bugs

TODO: Add here a list of the fixed bugs.

Known Issues

TODO: Add here a link to the SourceForge Bugs page, after filtering bugs (Assignee Any, Status Open, Category Any, Group 1.2).

  • Early releases of XULRunner 1.9.1 may cause an SWT exception that prevents from opening an editor (as well as any browser-based ui component). More recent releases fix this bug (works fine with xulrunner- Alternatively, it is possible to specify XULRunner path to point to 1.9.0: edit "rodin.ini" and add the following line:

where "/usr/lib/xulrunner-" must be replaced with your actual XULRunner 1.9.0 install directory.

  • Using Rodin on GNOME desktop may result in a situation where buttons lock windows. To avoid this situation, it is needed to launch Rodin with
GDK_NATIVE_WINDOWS=1 /path_to_rodin/rodin

It's a GTK bug, referenced for Eclipse at [[1]]
See also Gnome and broken buttons.

  • A warning like the following one is displayed to the standard output when platform starts on GNOME desktop:
(rodin:17254): GLib-WARNING **: g_set_prgname() called multiple times

It's a GNOME bug. Information found there: [[2]]

  • The error log shows the following problem:
org.osgi.framework.BundleException: The bundle could not be resolved. Reason: Missing Constraint: Import-Package: org.eclipse.equinox.internal.util.event; version="1.0.0"
at org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolverError(

It's an Eclipse 3.5 bug. Information found there: [[3]]